Method, apparatus and computer program product for creating a wireless docking group

ABSTRACT

Method, apparatus, and computer program product embodiments are disclosed to enable simplified configuring of a wireless docking group for wireless devices by allowing a wireless device to communicate its capabilities and characteristics of one or more wireless devices within a wireless docking group, using a new Wireless Docking Protocol, to a wireless docking station that will use that information and the Wireless Docking Protocol to define an optimal set of connections for wireless devices in the wireless docking group.

FIELD

The field of the invention relates to wireless communication, and moreparticularly to creating a wireless docking group within a wirelessenvironment.

BACKGROUND

Modern society has adopted, and is becoming reliant upon, wirelesscommunication devices for various purposes, such as connecting users ofthe wireless communication devices with other users. Wirelesscommunication devices can vary from battery powered handheld devices tostationary household and/or commercial devices utilizing an electricalnetwork as a power source. Due to rapid development of the wirelesscommunication devices, a number of areas capable of enabling entirelynew types of communication applications have emerged.

Cellular networks facilitate communication over large geographic areas.These network technologies have commonly been divided by generations,starting in the late 1970s to early 1980s with first generation (1G)analog cellular telephones that provided baseline voice communications,to modern digital cellular telephones. GSM is an example of a widelyemployed 2G digital cellular network communicating in the 900 MHZ/1.8GHZ bands in Europe and at 850 MHz and 1.9 GHZ in the United States.While long-range communication networks, like GSM, are a well-acceptedmeans for transmitting and receiving data, due to cost, traffic andlegislative concerns, these networks may not be appropriate for all dataapplications.

Short-range communication technologies provide communication solutionsthat avoid some of the problems seen in large cellular networks.Bluetooth™ is an example of a short-range wireless technology quicklygaining acceptance in the marketplace. In addition to Bluetooth™ otherpopular short-range communication technologies include Bluetooth™ LowEnergy, IEEE 802.11 wireless local area network (WLAN), Wireless USB(WUSB), Ultra Wide-band (UWB), ZigBee (IEEE 802.15.4, IEEE 802.15.4a),and ultra high frequency radio frequency identification (UHF RFID)technologies. All of these wireless communication technologies havefeatures and advantages that make them appropriate for variousapplications.

Traditionally, docking station hardware has been used to plug in alaptop computer for use as a desktop computer, and to directly connectit with peripherals such as a monitor, keyboard, and other commonperipherals. Currently there are no standards for configuring an entirewireless docking environment. An individual peripheral may be wirelesslyconnected to a mobile device by means of manual or semi-automaticconfiguration. However, manually configuring a mobile device withmultiple peripherals in a wireless docking environment, includingwireless device discovery, selection, and connectivity setup, is acumbersome task requiring technical expertise and may generally theresult in a less than optimal wireless connectivity between the devices.

SUMMARY

Method, apparatus, and computer program product embodiments aredisclosed to enable simplified configuring of a wireless docking groupfor wireless devices by allowing a wireless device to communicate itscapabilities and characteristics of one or more wireless devices withina wireless docking group, using a new Wireless Docking Protocol to awireless docking station that will use that information and the WirelessDocking Protocol to define an optimal set of connections for wirelessdevices in the wireless docking group.

An example embodiment of the invention includes a method comprising thesteps of

forming a communication link between a wireless docking station and adockee device;

receiving, by the docking station, from the dockee device, informationabout the dockee device's capabilities and characteristics of one ormore wireless devices within a wireless docking group;

defining, by the docking station, one or more optimal connections forone or more of the wireless devices in the wireless docking group, basedon the received information; and

transmitting, by the docking station, to the dockee device, informationto enable formation of the one or more optimal connections for the oneor more devices in the wireless docking group.

An example embodiment of the invention further comprises a method forwireless docking, wherein the information is communicated using adocking protocol.

An example embodiment of the invention further comprises a method forwireless docking, wherein the wireless docking station joins aninfrastructure network having an access point, and forms a peer-to-peerconnection with the dockee device.

An example embodiment of the invention further comprises a method forwireless docking, by forming direct connections by the wireless dockingstation, with at least one of the one or more devices, based on thedefined optimal connections.

An example embodiment of the invention further comprises a method forwireless docking, wherein the communication link with the dockee deviceis a Wi-Fi direct network.

An example embodiment of the invention further comprises a method forwireless docking, wherein the communication link with the dockee deviceis a Tunneled Direct Link Setup connection.

In an example embodiment of the invention, a computer program productcomprising computer executable program code recorded on a computerreadable, non-transitory storage medium, the computer executable programcode, when executed by a computer processor, performing the steps in theexample methods recited above.

In an example embodiment of the invention, an apparatus, comprises:

at least one processor;

at least one memory including computer program code;

the at least one memory and the computer program code configured to,with the at least one processor, cause the device at least to:

form a communication link with a dockee device;

receive from the dockee device, information about the dockee device'scapabilities and characteristics of one or more wireless devices withina wireless docking group;

define one or more optimal connections for one or more of the wirelessdevices in the wireless docking group, based on the receivedinformation; and

transmit to the dockee device, information to enable formation of theone or more optimal connections for the one or more devices in thewireless docking group.

An example embodiment of the invention includes a method comprising thesteps of

forming a communication link between a wireless docking station and adockee device;

transmitting, by the dockee device to the docking station, informationabout the dockee device's capabilities and characteristics of one ormore wireless devices within a wireless docking group; and

receiving, by the dockee device from the docking station, information toenable formation of the one or more optimal connections for the one ormore devices in the wireless docking group.

An example embodiment of the invention further comprises a method forwireless docking, wherein the information is communicated using adocking protocol.

An example embodiment of the invention wherein the method furthercomprises forming, by the dockee device, one or more wirelessconnections with one or more other devices based on the receivedinformation.

In an example embodiment of the invention, a computer program productcomprising computer executable program code recorded on a computerreadable, non-transitory storage medium, the computer executable programcode, when executed by a computer processor, performing the steps in theexample methods recited above.

In an example embodiment of the invention, an apparatus, comprises:

at least one processor;

at least one memory including computer program code;

the at least one memory and the computer program code configured to,with the at least one processor, cause the device at least to:

form a communication link between the apparatus and a wireless dockingstation;

transmit to the docking station, information about the apparatus'capabilities and characteristics of one or more wireless devices withina wireless docking group; and

receive from the docking station, information to enable formation of theone or more optimal connections for the one or more devices in thewireless docking group.

The resulting example embodiments enable simplified configuring of awireless docking environment for wireless devices, a consistent andeasier user experience, fewer steps for a user to setup Wi-Ficonnectivity, no need for a user to understand the details of Wi-Ficonnection setup, and more optimal Wi-Fi connectivity settings.

DESCRIPTION OF THE FIGURES

FIG. 1A is an example embodiment of a Dockee device A comprising asingle Wi-Fi communications protocol stack operating in Wi-Fi Directmode, and an example wireless Docking Station device F comprising a dualWi-Fi communications protocol stack operating in Wi-Fi Direct andInfrastructure modes, performing a wireless docking procedure over aWi-Fi Direct communication connection, according to an embodiment of thepresent invention.

FIG. 1B is an example embodiment of a Dockee device A′ comprising a WLANcommunications protocol stack and a Tunneled Direct Link Setupcommunications protocol stack and an example wireless Docking Stationdevice F comprising a WLAN communications protocol stack and a TunneledDirect Link Setup communications protocol stack, performing a wirelessdocking procedure over a Tunneled Direct Link Setup communicationconnection, according to an embodiment of the present invention.

FIG. 1C is an example embodiment of a Dockee device A″ comprising a dualWi-Fi communications protocol stack operating in Wi-Fi Direct andInfrastructure modes and an example wireless Docking Station device Fcomprising a dual Wi-Fi communications protocol stack operating in Wi-FiDirect and Infrastructure modes, performing a wireless docking procedureover a Wi-Fi Direct communication connection, according to an embodimentof the present invention.

FIG. 1D is an example embodiment of the Dockee device A″ of FIG. 1C,comprising an example dual radio embodiment with the dual Wi-Ficommunications protocol stack. One protocol stack operates in Wi-FiDirect mode. The other protocol stack operates in Infrastructure mode.Each protocol stack has its respective digital baseband transmissionpath outputting its signal to the radio. On the receive side, therespective radio outputs the received signal to the digital basebandtransmission path of the respective protocol stack, according to anembodiment of the present invention.

FIG. 2A is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi infrastructure networkconfiguration of a mobile phone having a single Wi-Fi stack supportingWi-Fi Direct and Infrastructure operation modes, connected as a clientto an access point, and a single stack printer that supports Wi-FiProtected setup, which is also connected to the access point, thetransformation creating a wireless docking environment by means of aDocking Station having a dual Wi-Fi stack supporting Wi-Fi Direct andInfrastructure operation modes, performing a wireless docking procedureto create the wireless docking environment, with the mobile phone in therole of a Dockee, the printer as a peripheral, and the access pointproviding Wi-Fi connectivity in the environment, according to anembodiment of the present invention.

FIG. 2B is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi infrastructure networkconfiguration of a mobile phone having a dual protocol stack supportingTDLS and Infrastructure operation modes, with a WLAN communicationsprotocol stack and a Tunneled Direct Link Setup communications protocolstack, connected as a client to an access point, and a single stackprinter that supports Wi-Fi Protected setup, which is also connected tothe access point, the transformation creating a wireless dockingenvironment by means of a Docking Station having a dual protocol stacksupporting TDLS and Infrastructure operation modes, with a WLANcommunications protocol stack and a Tunneled Direct Link Setupcommunications protocol stack, performing a wireless docking procedureto create the wireless docking environment, with the mobile phone in therole of a Dockee, the printer as a peripheral, and the access pointproviding Wi-Fi connectivity in the environment, according to anembodiment of the present invention.

FIG. 2C is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi infrastructure networkconfiguration of a mobile phone having a dual Wi-Fi communicationsprotocol stack supporting Wi-Fi Direct and Infrastructure operationmodes, connected as a client to an access point, and a single stackprinter that supports Wi-Fi Protected setup, which is also connected tothe access point, the transformation creating a wireless dockingenvironment by means of a Docking Station having a dual Wi-Ficommunications protocol stack supporting Wi-Fi Direct and Infrastructureoperation modes, performing a wireless docking procedure to create thewireless docking environment, with the mobile phone in the role of aDockee, the printer as a peripheral, and the access point providingWi-Fi connectivity in the environment, according to an embodiment of thepresent invention.

FIG. 2D is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi network configuration of a mobilephone having a single Wi-Fi stack supporting Wi-Fi Direct andInfrastructure operation modes, connected to a single stack printer thatsupports Wi-Fi Direct, the transformation creating a wireless dockingenvironment by means of a Docking Station having a dual Wi-Fi stacksupporting Wi-Fi Direct and Infrastructure operation modes, performing awireless docking procedure to create the wireless docking environment,with the mobile phone in the role of a Dockee, the printer as aperipheral, and the Docking Station providing Wi-Fi connectivity in theenvironment, according to an embodiment of the present invention.

FIG. 2E is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi infrastructure networkconfiguration of a mobile phone having a dual Wi-Fi communicationsprotocol stack supporting Wi-Fi Direct and Infrastructure operationmodes, connected as a client to an access point, connected to a singlestack printer that supports Wi-Fi Direct, the transformation creating awireless docking environment by means of a Docking Station having a dualWi-Fi communications protocol stack supporting Wi-Fi Direct andInfrastructure operation modes, performing a wireless docking procedureto create the wireless docking environment, with the mobile phone in therole of a Dockee, the printer as a peripheral, and the access pointproviding Wi-Fi connectivity in the environment, according to anembodiment of the present invention. The printer 100E is shown having aWi-Fi Direct link 224 to the Docking station 100F.

FIG. 2F is a wireless network diagram of an example embodiment, showingthe creation of a wireless docking environment by means of a DockingStation having a dual Wi-Fi stack supporting Wi-Fi Direct andInfrastructure operation modes, performing a wireless docking procedureto create the wireless docking environment that includes a mobile phonehaving a single Wi-Fi stack supporting Wi-Fi Direct and Infrastructureoperation modes, which assumes the role of a Dockee, the mobilephone/Dockee forwarding a user indication to the Docking Station that asingle stack printer that supports Wi-Fi Direct is to be included in thewireless docking environment, the Docking Station providing Wi-Ficonnectivity in the environment, according to an embodiment of thepresent invention.

FIG. 2G is a wireless network diagram of an example embodiment, showingthe creation of a wireless docking environment by means of a DockingStation having a dual Wi-Fi stack supporting Wi-Fi Direct andInfrastructure operation modes, performing a wireless docking procedureto create the wireless docking environment that includes a mobile phonehaving a dual Wi-Fi communications protocol stack supporting Wi-FiDirect and Infrastructure operation modes, connected as a client to anaccess point, the mobile phone assuming the role of a Dockee, the mobilephone/Dockee forwarding a user indication to the Docking Station that asingle stack printer that supports Wi-Fi Direct is to be included in thewireless docking environment, the mobile phone/Dockee providing Wi-Ficonnectivity in the environment, according to an embodiment of thepresent invention. The printer 100E is shown having a Wi-Fi Direct link232 to the Docking station 100F.

FIG. 3 is an example embodiment of a sequence diagram of the DockingStation performing the Wireless Docking Protocol procedure to create thewireless docking environment with the Dockee device, as shown in FIGS.2A to 2G, according to an embodiment of the present invention.

FIG. 4 is an example flow diagram of operational steps of an exampleembodiment of the Wireless Docking Protocol procedure to create thewireless docking environment, as shown in FIGS. 2A to 2G, according toan embodiment of the present invention.

FIGS. 5A to 5E are, collectively, an example flow diagram of operationalsteps of an example embodiment of the Wireless Docking Protocolprocedure in the Docking Station, to define the Wi-Fi connectivitysettings for a peripheral device in a wireless docking environment,using the network configuration program, according to an embodiment ofthe present invention.

FIG. 6 is an example flow diagram of operational steps of an exampleembodiment of the Wireless Docking Protocol procedure in the Dockeedevice, to transmit to the docking station, information it has gatheredabout the dockee device's capabilities and characteristics of one ormore wireless devices within a wireless docking group; and receive fromthe docking station, information to enable formation of the one or moreoptimal connections for the one or more devices in the wireless dockinggroup, according to an embodiment of the present invention.

DISCUSSION OF EXAMPLE EMBODIMENTS OF THE INVENTION

Wi-Fi refers to the family of related IEEE 802.11 specifications thatspecify methods and techniques of wireless local area network (WLAN)operation. Examples include the IEEE 802.11b and 802.11g wireless localarea network specifications, which have been a staple technology fortraditional Wi-Fi applications in the 2.4 GHz ISM band. Emergingbroadband applications have stimulated interest in developing veryhigh-speed wireless networks for short range communication, for example,the IEEE 802.11n, the planned IEEE 802.11ac, and the planned IEEE 802.11ad WLAN specifications that are to provide a very high throughput inhigher frequency bands. Wi-Fi applications include 802.11 products suchas consumer electronics, telephones, personal computers, and accesspoints for both for home and small office.

In an example application of Wi-Fi, a wireless router may be connectedthrough a cable modem or DSL modem to the Internet and serves as awireless access point for personal computers equipped with a wirelessnetwork interface card and for other wireless devices such as wirelessrepeaters using a Wi-Fi standard. Setting up a wireless router Wi-Finetwork includes configuring the nodes of the network with securityfeatures enabled by the Wi-Fi network standard.

Conventional Wi-Fi networks include an access point to which areconnected one or more computers and peripheral devices by wired andwireless connections. Wi-Fi networks are typically set up asinfrastructure networks, where the access point is a central hub towhich Wi-Fi capable devices are connected. The devices do notcommunicate directly with one another, but communicate indirectlythrough the access point.

Network setup has been simplified by the Wi-Fi Protected Setup™ systemthat is included in most access points. The Wi-Fi Alliance published theWi-Fi Protected Setup (WPS) specification 1.0, Wi-Fi Protected SetupSpecification, Version 1.0h, December 2006 (incorporated herein byreference). The Wi-Fi Simple Configuration (WSC) Specification, Version2.0, Dec. 20, 2010, (incorporated herein by reference), updates theWi-Fi Protected Setup Specification, Version 1.0h. The acronym WSC, forWi-Fi Simple Configuration Specification, may be used interchangeablywith the acronym WPS, for Wi-Fi Protected Setup. Wi-Fi Protected Setupfacilitates the initial setting up of 802.11 devices in a Wi-Fiinfrastructure network so that they may be more easily configured withsecurity features and so that that new Wi-Fi devices may be added to thenetwork. Wi-Fi Protected Setup allows access points to be set up byentering a PIN. The Protected Setup system uses this information to senddata to a computer connected to the access point, to complete thenetwork setup. Wi-Fi Protected Setup defines new 802.11 informationelements (IE) that are included in beacons, probe requests and proberesponses. The purpose of these IEs is to advertise the presence ofdevices that are capable of performing Wi-Fi Protected Setup operations.

The Wi-Fi Protected Setup 1.0 standard defines three types of componentsin a network: a Registrar, an Enrollee, and an Access Point (AP). ARegistrar is a component with the authority to issue and revokecredentials to a network. A Registrar may be integrated into an AP or itmay be separate from the AP. An Enrollee is a component seeking to joina wireless LAN network. An Authenticator is an AP functioning as a proxybetween a Registrar and an Enrollee. A Registrar wireless deviceconfigures the Enrollee wireless device, and the AP acts as anAuthenticator to proxy the relevant messages between the Registrar andthe Enrollee. The messages exchanged in the session are a series ofExtensible Authentication Protocol (EAP) request/response messages,ending with the Enrollee reconnecting to the network with its newconfiguration. EAP is an authentication framework defined in RFC 5247,for providing the transport and usage of keying material and parametersneeded to establish a secure Wi-Fi network. The Wi-Fi SimpleConfiguration Specification, Version 2.0, Dec. 20, 2010, (incorporatedherein by reference), updates the Wi-Fi Protected Setup Specification,Version 1.0h.

A standalone AP that supports Wi-Fi Protected Setup, includes a built-inRegistrar and does not use an external Registrar. In initial WLAN setupwith Wi-Fi Protected Setup, when initializing in a standalone mode, aWi-Fi Protected Setup AP automatically chooses a random SSID andchannel. A standalone AP that includes a Wi-Fi Protected SetupRegistrar, issues keys to Enrollees via the Registration Protocol.

When an Enrollee is initialized, it looks for Beacons from APs and sendsprobe-requests with the WSC information element (IE) into eitherselected networks or into each network sequentially. It may also sendprobe-requests to each 802.11 channel with the WSC IE included. It looksfor the WSC IE in probe-responses that it receives and can engage withone or more Registrars to further discover Registrar capabilities and tosee if the user has selected a Registrar. The Enrollee may continuelooking for selected Registrar flags in Beacons, probe-responses and anyM2 messages and may cease scanning when it finds a Registrar indicatingthat it is prepared to configure the Enrollee.

The following example describes an example in-band setup procedure usingWi-Fi Protected Setup for adding Member devices using a StandaloneAP/Registrar. The user may convey the Enrollee's device password to theAP/Registrar using keyboard entry or an out-of-band channel with NFCConnection Handover. This example does not show the exchange ofpreliminary M1 and M2D messages that may take place after the probemessage exchange, because the Enrollee may be waiting for the user toconfigure the AP/Registrar with the Enrollee's device password.

1. The Enrollee sends its Discovery data in a probe request to a Wi-FiProtected Setup AP or ad hoc wireless Registrar. The AP or wirelessRegistrar responds with its own Discovery data in the probe response.

2. The user may be prompted to enter the Enrollee's device password intothe AP/Registrar using a keypad interface or an out-of-band channel.

3. The Enrollee connects and initiates the IEEE 802.1X port-basedNetwork Access Control procedure for port-based authentication.

4. The Enrollee and Registrar exchange messages M1-M8 to provision theEnrollee.

5. The Enrollee disassociates and reconnects, using its new WLANauthentication Credential. The Enrollee is now connected to the networkwith its new configuration.

The Wi-Fi Alliance has developed a Wi-Fi Peer-to-Peer technology namedWi-Fi Direct™ that is specified in the Wi-Fi Alliance Peer-to-PeerSpecification, October 2010 (incorporated herein by reference). Wi-FiDirect, is also referred to herein as Wi-Fi Peer-to-Peer or Wi-Fi P2P.Wi-Fi Direct enables IEEE 802.11a, g, or n devices to connect to oneanother, peer-to-peer, without prior setup or the need for wirelessaccess points. Wi-Fi Direct embeds a software access point into anydevice, which provides a version of Wi-Fi Protected Setup. When a deviceenters the range of the Wi-Fi Direct host, it can connect to it and thengather setup information using a Wi-Fi Protected Setup transfer. Devicesthat support Wi-Fi Direct may discover one another and advertiseavailable services. Wi-Fi Direct devices support typical Wi-Fi rangesand the same data rates as can be achieved with an 802.11a, g, or ninfrastructure connection. When a device enters the range of the Wi-FiDirect host, it may connect to it using the existing protocol, and thengather setup information using a Wi-Fi Protected Setup 2.0 transfer.

Wi-Fi Direct-certified devices may create direct connections betweenWi-Fi client devices without requiring the presence of a traditionalWi-Fi infrastructure network of an access point or router. Wi-FiDirect-certified devices support connection with existing legacy Wi-Fidevices using the IEEE 802.11a/g/n protocols. Wi-Fi Direct DeviceDiscovery and Service Discovery features allow users to identifyavailable devices and services before establishing a connection, forexample, discovering which Wi-Fi networks have a printer. Wi-Fi Directdevices may use Wi-Fi Protected Setup to create connections betweendevices.

A Wi-Fi Direct device is capable of a peer-to-peer connection and maysupport either an infrastructure network of an access point or router ora peer-to-peer (P2P) connection. Wi-Fi Direct devices may joininfrastructure networks as stations (STAs) and may support Wi-FiProtected Setup enrollee functionality. Wi-Fi Direct devices may connectby forming Groups in a one-to-one or one-to-many topology. The Groupsfunctions in a manner similar to an infrastructure basic service set(BSS). A single Wi-Fi Direct device will be the Group Owner (GO) thatmanages the Group, including controlling which devices are allowed tojoin and when the Group is started or terminated. The Group Owner (GO)will appear as an access point to legacy clients devices.

Wi-Fi Direct devices include a Wi-Fi Protected Setup Internal Registrarfunctionality and communication between Clients in the Group. Wi-FiDirect devices may be a Group Owner (GO) of a Group and may be able tonegotiate which device adopts this role when forming a Group withanother Wi-Fi Direct device. A Group may include both Wi-Fi Directdevices and legacy devices (i.e., that are not compliant with the Wi-FiAlliance Peer-to-Peer Specification). Legacy Devices can only functionas Clients within a Group.

Wi-Fi Direct devices may support Discovery mechanisms. Device Discoveryis used to identify other Wi-Fi Direct devices and establish aconnection by using a scan similar to that used to discoverinfrastructure access points. If the target is not already part of aGroup, a new Group may be formed. If the target is already part of aGroup, the searching Wi-Fi Direct device may attempt to join theexisting Group. Wi-Fi Protected Setup may be used to obtain credentialsand authenticate the searching Wi-Fi Direct device. Wi-Fi Direct devicesmay include Service Discovery that enables the advertisement of servicessupported by higher layer applications to other Wi-Fi Direct devices.Service Discovery may be performed at any time (e.g. even before aconnection is formed) with any other discovered Wi-Fi Direct device.

A Group may be created by a single Wi-Fi Direct device, such as whenconnecting a legacy device. When forming a connection between two Wi-FiDirect devices, a Group may be formed automatically and the devices maynegotiate to determine which device is the Group Owner. The Group Ownermay decide if this is a temporary (single instance) or persistent(multiple, recurring use) Group. After a Group is formed, a Wi-Fi Directdevice may invite another Wi-Fi Direct device to join the Group. Thedecision of whether or not to accept an invitation may be left to theinvited Wi-Fi Direct device.

Concurrent Wi-Fi Direct Devices may participate in multiple Groups,simultaneously, each group requires own Wi-Fi stack. A Wi-Fi DirectDevice that may be in a Group while maintaining a WLAN infrastructureconnection at the same time is considered a Concurrent Device. This is atypical dual stack case, as presented in FIGS. 2C, 2E and 2G. Forexample, a laptop connected directly to a printer while simultaneouslyusing a WLAN connection is operating as a Concurrent Device. Concurrentconnections may be supported by a single radio and may supportconnections on different channels. Concurrent operation may be supportedby multiple protocol stacks, for example, one for operation as aWLAN-STA and one for operating as a Wi-Fi Direct device. For example,two separate physical MAC entities may be maintained, each associatedwith its own PHY entity, or they may use a single PHY entity supportingtwo virtual MAC entities.

The Wi-Fi Peer-to-Peer Technical Specification v1.1, 2010 published bythe Wi-Fi Alliance, provides for provisioning in Wi-Fi Direct networks.Provisioning is a phase of peer-to-peer group formation in whichcredentials for the peer-to-peer group are exchanged based on the use ofWi-Fi Simple Configuration. Credentials are information that is requiredto join a peer-to-peer group as defined in the Wi-Fi SimpleConfiguration Specification.

To allow for peer-to-peer device configuration, peer-to-peer devices maydelay starting the provisioning phase until the expiration of the largerof the peer-to-peer group owner's (GO) configuration time and thepeer-to-peer client's client configuration time, based on respectiveconfiguration timeout attributes exchanged during a preceding groupowner negotiation.

The peer-to-peer device selected as peer-to-peer group owner (GO) duringgroup owner negotiation may start a peer-to-peer group session using thecredentials it intends to use for that group. The peer-to-peer groupowner (GO) may use the operating channel indicated during group ownernegotiation, if available. The peer-to-peer client may connect to thepeer-to-peer group owner to obtain credentials. If the operating channelis not available the peer-to-peer group owner may use another channelfrom a channel list attribute sent in the group owner negotiationconfirmation frame. The peer-to-peer client may have to scan to find thepeer-to-peer group owner if the intended operating channel is notavailable. A group formation bit in a peer-to-peer group capabilitybitmap of the peer-to-peer capability attribute may be set to one untilprovisioning succeeds.

Provisioning may be executed in Wi-Fi Direct networks, as described inthe Wi-Fi Simple Configuration (WSC) Specification, Version 2.0, Dec.20, 2010: The peer-to-peer group owner (GO) may serve the role as theaccess point with an internal registrar. It will only allow associationby the peer-to-peer device that it is currently with in a groupformation. Since the user has entered the WSC PIN or triggered the WSCpushbutton functionality on both devices, the registrar may send an m2message in response to an m1 message. The peer-to-peer client may servethe role as the STA enrollee. It may associate to the peer-to-peerdevice that it is currently with in the group formation.

If provisioning fails, then group formation ends and the peer-to-peergroup owner (GO) may end the peer-to-peer group session. If provisioningfails, the peer-to-peer device may retry group formation or return todevice discovery. On successful completion of provisioning in Wi-FiDirect networks, the peer-to-peer group owner (GO) may set the groupformation bit in the peer-to-peer group capability bitmap of thepeer-to-peer capability attribute to zero. At this point thepeer-to-peer client may join the peer-to-peer group in the Wi-Fi Directnetwork, using the credentials supplied during provisioning.

A next generation IEEE 802.11 WLAN standard is being currently developedas the IEEE 802.11 TGz standard, which includes the feature of TunneledDirect Link Setup (TDLS) with Channel Switching. This feature enablestwo mobile wireless devices (STAs) in an infrastructure BSS to directlyexchange frames of data over a direct data transfer link, withoutrequiring the access point (AP) in the infrastructure BSS to relay theframes.

One of the methods provided by the Wi-Fi Simple ConfigurationSpecification, Version 2.0, Dec. 20, 2010, (incorporated herein byreference), is the Near-Field Communication (NFC) method, in which theuser brings a new wireless client device (STA) close to an access point(AP) or Registrar of the Network to allow near field communicationbetween the devices.

Near field communication technologies, such as radio frequencyidentification (RFID) technologies, comprise a range of RF transmissionsystems, for example standardized and proprietary systems for a largenumber of different purposes, such as product tagging for inventoryhandling and logistics, theft prevention purposes at the point of sale,and product recycling at the end of the life-cycle of the taggedproduct. In addition to RFID technologies, Near Field Communication(NFC) technology has recently evolved from a combination of existingcontactless identification and interconnection technologies. NFC is botha “read” and “write” technology. Communication between twoNFC-compatible devices occurs when they are brought within closeproximity of each other: A simple wave or touch can establish an NFCconnection, which is then compatible with other known wirelesstechnologies, such as Bluetooth™ or wireless local area network (WLAN).

Near-field communication (NFC) technology used in the Wi-Fi ProtectedSetup (WPS) standard, communicates between two NFC Devices or between anNFC Device and an NFC Tag via magnetic field induction, where two loopantennas are located within each other's near field, effectivelyenergizing a wireless contact by forming an air-core transformer. Anexample NFC radio operates within the unlicensed radio frequency ISMband of 13.56 MHz, with a bandwidth of approximately 2 MHz over atypical distance of a few centimeters. The NFC radio may be affixed to anew wireless client device (STA) and the user brings the NFC radio onthe device close to an access point (AP) or Registrar of the Network toallow near field communication between the devices. NFC technology is anextension of the ISO/IEC 14443 proximity-card standard (incorporatedherein by reference) for contactless smartcards and radio frequency ID(RFID) devices, which combines the interface of a contactless smartcardand a reader into a single device, and uses the ISO/IEC 18092 NFCcommunication standard (incorporated herein by reference) to enabletwo-way communication. An NFC radio may communicate with both existingISO/IEC 14443 contactless smartcards and readers, as well as with otherNFC devices by using ISO/IEC 18092. The NFC Forum™, a non-profitindustry association, has released specifications that enable differentoperation modes called: tag emulation, read/write mode, and peer to peercommunication. Furthermore, NFC Forum has defined specifications for NFCData Exchange Format (NDEF), NFC Tag Types, NFC Record Type Definition,and Connection Handover Specification. See, for example, ConnectionHandover Technical Specification, NFC Forum™, Connection Handover 1.1,NFCForum-TS-ConnectionHandover_(—)1.1, 2008-Nov.-06 (incorporated hereinby reference). The ISO/IEC 18092 standard defines communication modesfor Near Field Communication Interface and Protocol (NFCIP-1) usinginductively coupled devices operating at the center frequency of 13.56MHz for interconnection of computer peripherals. The ISO/IEC 18092standard specifies modulation schemes, codings, transfer speeds andframe format of the RF interface, initialization schemes, conditionsrequired for data collision control during initialization, and atransport protocol including protocol activation and data exchangemethods.

The Wi-Fi Protected Setup (WPS) 1.0 specification published by the Wi-FiAlliance, Wi-Fi Protected Setup Specification, Version 1.0h, December2006, defines a near-field communication (NFC) setup method for IEEE802.111 WLAN Infrastructure setup that includes an access point (AP),and is currently the only official Wi-Fi Protected Setup specification.The access point (AP) defines the roles of registrar and enrollee forthe requesting device and the selecting device. The Wi-Fi ProtectedSetup (WPS) 2.0 specification (to be published) updates the NFC setupmethod for WLAN Infrastructure mode that includes an access point (AP).Current WLAN device-to-device technologies include the IEEE 802.11 IBSS(Ad Hoc), Wi-Fi networks, and Bluetooth.

The basic handover to a Wi-Fi carrier stores wireless LAN parameters andcredentials on NFC Forum Tags as part of its Wi-Fi Protected Setup (WPS)specification 1.0. The information is stored in the payload of an NFCData Exchange Format (NDEF) record identified by the mime-type“application/vnd.wfa.wsc”, known as the “WPS Record”. The wireless LANparameters and credentials information provided inside a WPS Recordincludes the IEEE 802.11 Service Set Identifier (SSID), authenticationand encryption type deployed by the wireless network, the secret networkkey that a wireless station needs to authenticate with the network, andthe MAC address of the device receiving the configuration (if unknown,this address is set to all-zeros). The Wi-Fi Protected Setupspecification 1.0 uses the term “Registrar” for a device that is able toprovide WLAN credentials and “Enrollee” for a device that wants to joina wireless network.

In the Wi-Fi Simple Configuration Specification, Version 2.0, Dec. 20,2010, a Handover Requester with Wi-Fi capability may format an NFCHandover Request Message in the NFC Data Exchange Format (NDEF), thatindicates that the requester is an IEEE 802.11 device, but which doesnot include any configuration information. A Handover Request may besent via the NFC link in at least two scenarios: [1] the requester maynot have yet joined a wireless domain or [2] even if the requester isalready member of a WLAN network, a peer device may be in differentnetwork and thus a Connection Handover is required to obtain the peerdevice's credentials. In the Wi-Fi Protected Setup specification 2.0,the Handover Selector would deduce from this message that the HandoverRequester supports a Wi-Fi certified IEEE 802.11 radio. In the Wi-FiProtected Setup specification 2.0, if the Handover Selector is a Wi-Fidevice with wireless connectivity, it should respond with an NFCHandover Select Message in the NFC Data Exchange Format (NDEF), with aconfiguration record that includes credentials, such as network index,SSID, authentication type, encryption type, network key, and MACaddress.

The NFC Data Exchange Format (NDEF) specification, NFC Forum DataExchange Format (NDEF) Specification, NFC Forum™, 2006 (incorporatedherein by reference), defines a common data format for NFC devices toexchange application or service specific data. An NDEF message isconstructed of a number of NDEF records, with the first and the lastrecord providing message begin and end markers. Between two NFC Devices,NDEF messages may be exchanged over the NFC Logical Link ControlProtocol (LLCP) protocol, specified in NFC Forum Logical Link ControlProtocol Specification, NFC Forum™, 2009 (incorporated herein byreference). The NFC Connection Handover specification, NFC ForumConnection Handover Specification, NFC Forum™, 2008 (incorporated hereinby reference), defines the exchange of NDEF messages between two NFCDevices in a negotiated handover to discover and negotiate alternativewireless communication technologies.

The Handover Requester in the Wi-Fi Protected Setup specification 2.0,would then typically use the SSID and Network Key to enroll on the sameWi-Fi network to which the Handover Selector is connected. Furtherpossible actions depend on the provision of an IP address identifyingthe Handover Selector, the available services, and the HandoverRequester's intended activity.

The method, apparatus, and computer program product embodimentsdisclosed herein enable simplified configuring of a wireless dockingenvironment for wireless devices, using Wi-Fi Protected Setup and Wi-FiDirect. Optionally, NFC Connection Handover may be used to initiate theWi-Fi Protected Setup process during configuring of the wireless dockingenvironment.

Example Wireless Docking Environments

Wireless docking is referred to herein as connecting a mobile device toa group of peripheral devices wirelessly. Typical peripherals includee.g. display, input devices (mouse, keyboard, touch-screen), massstorage, printer etc.

The following are terms used herein to describe example features of awireless docking environment, according to an embodiment of theinvention:

Docking Environment:

-   -   a group of peripherals that belong together.    -   a docking environment may be configured by:        -   adding, or removing, peripherals from the docking            environment needs deliberate action    -   a Dockee may expect to automatically connect with all        peripherals that are available in the environment.

Dockee:

-   -   a portable product (e.g. smart phone, netbook, laptop, camera)        that is brought into the docking environment and uses the        peripherals.

Docking Station:

-   -   a device that coordinates the setup of connections between        Dockee and all peripherals in the environment    -   in addition it may also provide the connection between Dockee        and legacy peripherals

Peripheral:

-   -   e.g. mouse, keyboard, USB hard drive, webcam, display, . . .    -   may be connected to Dockee (wireless) or Docking Station (wired        or wireless)

The docking environment may be divided to the following types:

-   -   Centralized Docking Environment        -   Dockee connects to peripherals through Docking Station.        -   Dockee will have only one wireless connection; to Docking            Station.    -   Distributed Docking Environment        -   Dockee connects to each peripheral directly.        -   Dockee have own wireless connection for each peripheral        -   (In case of Wi-Fi there may be only single WLAN network            where multiple peripherals are attached.)    -   Hybrid Docking Environment        -   Combination of centralized and distributed environments,            i.e. some of the peripherals are connected directly and some            through Docking Station.

Wi-Fi has three different network operating modes; Basic Service Set(BSS), i.e., an Infrastructure network, Independent Basic Service Set(IBSS), i.e., an Ad Hoc network, and Peer-To-Peer (P2P), i.e., a Wi-FiDirect network. Conventionally, each WLAN type requires its ownindependent WLAN protocol stack with an independent state machine.Advanced devices such as laptops etc. may be able to simultaneouslyoperate on different network types using a dual/multi-stack WLANimplementation, but such complexity cannot be assumed for simplerdevices such as digital cameras. However, in certain wireless dockingscenarios, there is need for multi-WLAN type operation. The standardWi-Fi Protected Setup operation does not take the network limitations ofsimpler devices into consideration and does not consider dependenciesthat may exist between WLAN networks. The standard Wi-Fi Protected Setupprocedure does not consider specific wireless docking requirements, suchas latency between a Dockee device and a Docking Station.

Embodiments of the invention enable simplified configuring of a wirelessdocking group for wireless devices by allowing a wireless device tocommunicate its capabilities and characteristics of one or more wirelessdevices within a wireless docking group, using a new Wireless DockingProtocol to a wireless Docking Station that will use that informationand the Wireless Docking Protocol to define an optimal set ofconnections for wireless devices in the wireless docking group.

Embodiments of the invention enable a Dockee device to connect andmaintain network connectivity while connecting to wireless DockingStation.

Embodiments of the invention enable a Dockee to communicate itscapabilities and characteristics of one or more wireless devices withina wireless docking group to the Docking Station. The Docking Stationwill carry out actions to enable connectivity between Dockee and DockingStation and also between Dockee and peripheral devices and Access Point(AP). The dataset of capabilities and characteristics sent by the Dockeedevice to the Docking Station are collectively referred to herein as the“network configuration program” information. Examples of the networkconfiguration program 144 include the Smart Connectivity Setup Protocoland the Universal Plug and Play (UPnP) Protocol. The Wireless DockingProtocol transfers the network configuration program 144 informationfrom the Dockee device to the Docking Station.

In example embodiments of the invention, final connectivity settings maybe made based on the minimum requirements for the Dockee (e.g. awireless docking standard may define minimum Wi-Fi capabilityrequirements for the Dockee and Docking Station). However, during setupphase of the docking environment, the Dockee device's specificconnectivity capabilities may be utilized for creating temporaryconnections, if needed.

In example embodiments of the invention, the user may be instructed viaDockee's user interface with additional guidance, when needed.

Embodiments of the invention build on Wi-Fi Protected Setup and Wi-FiDirect and add a new Wireless Docking Protocol (WDP) that enablessignaling and configuration between all related entities. Embodiments ofthe invention allow legacy devices to operate in this environment.

The Dockee may potentially be any kind of device, from laptop to digitalcamera, and thus embodiments of the invention accommodate both singleand dual protocol stack Dockees.

In example embodiments of the invention, the Dockee has specific supportfor wireless docking. The Docking Station implements dual connectivityto ensure enough flexibility for the connectivity, and enable allrelevant wireless docking scenarios. The Docking Station acts as abridge when connected to an access point. When working without Internetconnectivity, the Docking Station may act as a Dynamic HostConfiguration Protocol (DHCP) server, as defined in Wi-Fi Direct.

In example embodiments of the invention, when an Infrastructure networkis available, Tunneled Direct Link Setup (TDLS) may be usable tooptimize architecture and data path, instead of using Wi-Fi Direct. Whenusing TDLS, two Infrastructure client devices may form a direct linkbetween them, and data sent over that link need not be routed throughthe access point.

Scenario [1]—Single Stack Dockee with Wi-Fi Direct with ExistingInfrastructure Network

FIG. 1A is an example embodiment of a Dockee device 100A comprising asingle Wi-Fi communications protocol stack 202 operating in Wi-Fi Directmode, and an example wireless Docking Station device 100F comprising adual Wi-Fi communications protocol stack 202′ and 203′ operating inWi-Fi Direct and Infrastructure modes, performing a wireless dockingprotocol 142 procedure over a Wi-Fi Direct communication connection 120,according to an embodiment of the present invention.

The wireless Docking Station device 100F includes a processor 122′,which includes a single core CPU or multiple core central processingunit (CPU) 124′ and 125′, a random access memory (RAM) 126′, a read onlymemory (ROM) 127′, and interface circuits 128′ to interface with one ormore radio transceivers 208′, battery or house power sources, keyboard,display, etc. The RAM and ROM can be removable memory devices such assmart cards, SIMs, WIMs, semiconductor memories such as RAM, ROM, PROMS,flash memory devices, etc. The wireless Docking Station device 100F mayinclude an NFC circuit to communicate with an NFC circuit in mobilephone Dockee device 100A, to respond to an handover to the Wi-Fi Directcommunication connection 120.

The mobile phone Dockee device 100A includes a processor 122, whichincludes a dual core central processing unit 124 and 125, a randomaccess memory (RAM) 126, a read only memory (ROM) 127, and interfacecircuits 128 to interface with one or more radio transceivers 208,battery and other power sources, key pad, touch screen, display,microphone, speakers, ear pieces, camera or other imaging devices, etc.in the mobile phone Dockee device 100A. The RAM and ROM can be removablememory devices such as smart cards, SIMs, WIMs, semiconductor memoriessuch as RAM, ROM, PROMS, flash memory devices, etc. The mobile phoneDockee device 100A may include an NCI circuit to communicate with an NCIcircuit in Docking Station 100F, to initiate the handover to the Wi-FiDirect communication connection 120.

An example embodiment of the WLAN (Wi-Fi) wireless docking protocol 142program and network configuration program 144 may be computer codeinstructions stored in the RAM and/or ROM memory of the processor 122′in the wireless Docking Station device 100F, which when executed by thecentral processing units (CPU), carry out the functions of the exampleembodiments of the invention. The connectivity settings transmit buffer148 in the Docking Station 100F buffers the Wi-Fi connectivity settingsdetermined by the network configuration program 144. The connectivitysettings transmit buffer 148 may be a partition in the RAM memory 126′of the processor 122′ in the Docking Station 100F.

An example embodiment of the WLAN (Wi-Fi) wireless docking protocol 142program and network configuration program 144 may be computer codeinstructions stored in the RAM and/or ROM memory of the processor 122 inthe mobile phone Dockee device 100A, which when executed by the centralprocessing units (CPU), carry out the functions of the exampleembodiments of the invention. The gathered information transmit buffer146 in the Dockee device 100A buffers gathered information, includinginformation about the Dockee device's capabilities and characteristicsof one or more wireless devices within a wireless docking group. Thegathered information transmit buffer 146 may be a partition in the RAMmemory 126 of the processor 122 in the mobile phone Dockee device 100A.

FIG. 2A is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi infrastructure networkconfiguration of a mobile phone 100A having a single Wi-Fi stacksupporting Wi-Fi Direct and Infrastructure operation modes, connectedover link 120 as a client to an access point, and a single stack printer100E that supports Wi-Fi Protected setup, which is also connected to theaccess point, the transformation creating a wireless docking environmentby means of a Docking Station 100F having a dual Wi-Fi stack supportingWi-Fi Direct and Infrastructure operation modes, performing the WirelessDocking Protocol 142 procedure with the Dockee device 100A to create thewireless docking environment, with the mobile phone 100A in the role ofa Dockee connected over new link 120 to access point 100B, the printer100E as a peripheral connected over existing link 212 to Docking Station100F, and the access point 100B connected over new link 214 to DockingStation 100F, the access point providing Wi-Fi connectivity in theenvironment, according to an embodiment of the present invention.

In the example of FIG. 2A, the mobile phone 100A has a single Wi-FiDirect stack 202. The Mobile phone 100A is used to setup wirelessdocking environment. In the initial state of FIG. 2A, the user hascreated an Infrastructure network with two client devices; the mobilephone 100A and the printer 100E, using two Wi-Fi Protected Setup (WPS)procedures, between the mobile phone 100A and the AP 100B and betweenthe printer 100E and the AP 100B.

In the example of FIG. 2A, then user buys the Docking Station 100F tocreate a wireless docking environment, and the user wants to use theexisting mobile phone 100A (as a Dockee), the printer 100E (as aPeripheral) and the AP 100B (for Wi-Fi connectivity) for thatenvironment.

In example embodiments of the invention, a new protocol is employed tosetup the wireless docking environment, called Wireless Docking Protocol(WDP). In example embodiments of the invention, Dockee capabilities andcharacteristics of one or more wireless devices within a wirelessdocking group may be expressed in a standard format such as in XMLdocuments, according WDP XML Schemas. Actions required may also beexpressed in XML or in some other format. Both actions and configurationdata may be carried over different protocols. For instance, universalplug and play (UPnP) device control protocol may be used to carry outinformation exchange. Alternately, modifying the Wi-Fi Protected setupor Wi-Fi Direct protocols may be used to carry out information exchange.However, the format of WDP messages is not limiting in embodiments ofthe invention.

In example embodiments of the invention:

-   -   Both Dockee and Docking Station implement WDP    -   Docking Station may be at least dual stack device    -   Dockee and Docking Station may support Wi-Fi Direct    -   Wi-Fi Peripheral may support standard WPS

In setting up the wireless docking environment, the Docking Station hasthe primary role to play. The Dockee has an assistant role during thesetup of the wireless docking environment.

Peripherals may be legacy devices without specific wireless dockingsupport, thus only standard Wi-Fi Protected Setup (WPS) implementationmay be assumed for the peripherals.

Because setup of Wireless Docking environment requires some user actionin some embodiments, a user application, such as a setup wizard, may beuseful to give guidance to the user. The functions of such a setupwizard application would co-operate with the wireless docking protocol.

Example Wireless Docking Protocol

FIG. 3 is an example embodiment of a sequence diagram of the DockingStation 100F performing the Wireless Docking Protocol 142 procedure tocreate the wireless docking environment with the Dockee device 100A,100A′, or 100A″, as shown in FIGS. 2A to 2G, according to an embodimentof the present invention. The Wireless Docking Protocol 142 illustratedin FIG. 3 uses as its network configuration program 144, the SmartConnectivity Setup Protocol. The following description of the sequencediagram of FIG. 3 uses the message format for the Smart ConnectivitySetup Protocol.

The first step 340 in wireless docking environment setup is to createWi-Fi connectivity link 120 between Dockee 100A and Docking Station100F. The standard Wi-Fi Protected Setup (WPS) using NFC ConnectionHandover is a recommend method, since it can also carry wireless dockingspecific information) required to setup the Wi-Fi Direct network. TheDocking Station 100F may become Group Owner (GO) of the peer-to-peer(P2P) network (Wi-Fi Direct has the means to ensure that the correctdevice becomes Group Owner).

After the establishment of Wi-Fi and IP connectivity link 120 betweenthe Dockee 100A and Docking Station 100F, the WDP exchange may beperformed for initial handshake and status exchange with SmartConnectivity Setup Protocol messages WDP_Init_Request in step 342 andWDP_Init_Response in step 344.

In example embodiments of the invention, the Dockee 100A may use Wi-FiDirect Device Discovery and Service Discovery features to identify theprinter 100E and gather its interface characteristics and its services.In example embodiments of the invention, the Dockee 100A communicates adataset describing its own capabilities and the characteristics of theprinter 100E, for example, to the Docking Station 100F. The dataset ofcapabilities and characteristics sent by the Dockee device 100A to theDocking Station 100F is collectively referred to herein as the “networkconfiguration program” information. In example embodiments of theinvention, the “network configuration program” information is in aformat compatible with the network configuration program 144 thatcarries out the Smart Connectivity Setup Protocol. In exampleembodiments of the invention, the Wireless Docking Protocol transfersthe network configuration program information from the Dockee device100A to the Docking Station 100F in the format of the Smart ConnectivitySetup Protocol.

In this case, Docking Station 100F indicates in step 346 that it is notconfigured, and actual initial setup of wireless docking environment isinitiated. This may also trigger opening of the Wireless Docking Setupapplication (a wizard program to guide the user) on the Dockee 100A(unless already manually opened by the user).

Then in step 350, the Dockee 100A gathers information for the networkconfiguration program 144, which in this example is in the format of theSmart Connectivity Setup Protocol. The gathered information includesinformation about the Dockee device 100A's capabilities andcharacteristics of one or more wireless devices, such as the printer100E and access point 100B within a wireless docking group in FIG. 2A.Gathering information by the Dockee device 100A from wireless devices,such as the printer 100E and access point 100B, may be carried out, forexample, using Wi-Fi Direct Device Discovery and Service Discoveryfeatures or the ad hoc network device discovery. The gatheredinformation may be buffered in the gathered information transmit buffer146 in the Dockee device 100A.

In the next phase, the Dockee 100A may forward the gathered informationover link 120, including information about the Dockee device'scapabilities and characteristics of one or more wireless devices withina wireless docking group, in step 352 to Docking Station 100F by usingSmart Connectivity Setup Protocol WDP_SCS_Request message. The gatheredinformation includes:

-   -   Dockee device's Wi-Fi capabilities;    -   Maximum number of parallel WLAN networks (=number of implemented        Wi-Fi stacks)    -   Supported Wi-Fi modes; Infrastructure, Wi-Fi Direct, etc.    -   Supported Wi-Fi feature; TDLS, . . . .    -   Wi-Fi status per each available connection:    -   Network SSID, credentials (if willing to share)    -   Network type, configuration methods    -   Network type; P2P, Infrastructure . . . .    -   Credentials of the network, (if allowed to send).    -   Status (attached, is able to connect, or is aware of this        network)    -   Pairing mechanism: WPS (PBC, PIN, NFC), manual, other    -   IP configuration (IP address, DHCP status, DNS, etc)    -   Known Internet connections    -   Interface/network    -   Status (active, inactive)    -   Whether this information may be shared    -   Other information of similar type etc    -   Information on current WLAN networks (=Dockee is currently        attached to these networks);    -   Information about Internet connectivity        -   WLAN used for Internet connection by the Dockee        -   FFS; Other connectivity methods (like cellular) used for            Internet connectivity    -   Willingness to disconnect and change IP address    -   Known Wi-Fi peripherals    -   Information on the other Wi-Fi devices (peripherals) nearby;        either member of current WLAN network or detected during the        scanning.        -   Device type**) **) For example; during Wi-Fi Direct setup,            Primary or Secondary Device Type attribute may have been            sent to Dockee.        -   Device identification, e.g. Device name, IP address, MAC            address or such.        -   Currently used network and connectivity settings

*) Dockee should perform short Wi-Fi scanning to detect nearby WLANnetworks before sending this information. Credentials are sent toDocking Station only if stored on Dockee, i.e. WLAN network is known tothe Dockee.

After receiving gathered Wi-Fi information from the Dockee 100A, theDocking Station 100F may also perform Wi-Fi scanning to ensure that WLANnetworks (and Wi-Fi devices attached to that WLAN) are available at thelocation of the Docking Station. Due to different locations of theDockee and Docking Station, there may be differences in sensitivity ofreceived Wi-Fi radio signals and the applicable WLAN networks maydiffer.

After this phase, the Docking Station 100F should have enoughinformation to make proper Wi-Fi connectivity settings in step 360 forthe wireless docking environment using the network configuration program144, which in this example is the Smart Connectivity Setup Protocol.FIGS. 5A to 5E illustrate an example embodiment of a method the DockingStation 100F may use to determine the Wi-Fi connectivity settings for aperipheral device 100E in step 360, using the network configurationprogram 144. The Wi-Fi connectivity settings determined in step 360 maybe buffered in the connectivity settings transmit buffer 148 in theDocking Station 100F.

However, at this point Docking Station 100F may not yet know whatwireless peripherals may be added to the docking environment. Thus, theWi-Fi connectivity settings may need to changed in a later phase toenable connectivity for any additional Wi-Fi peripherals.

The Dockee 100A may have already sent some information on the potentialperipherals within WDP_SCS_Request. However, the user may explicitlyselect what wireless peripherals will be added to the environment inlater phases.

Then, in step 362, the Docking Station 100F transmits over link 120, theWi-Fi connectivity settings from its connectivity settings transmitbuffer 148, back to Dockee 100A with the Smart Connectivity SetupProtocol message WDP_SCS_Response. In specific cases, Docking Station100F may need to define temporary connectivity configurations which areused only during Initial Setup. This Smart Connectivity Setup ProtocolWDP_SCS_Response may also include instructions about potentialperipherals (listed in Smart Connectivity Setup ProtocolWDP_SCS_Request) as whether current connectivity towards that peripheralis still valid. If not valid, then Docking Station 100F may define newconnectivity settings for that peripheral and give necessary guidance tothe Dockee 100A. But, in general, Docking Station 100F may give guidancefor the user (via the Dockee 100A's user interface application) anddefine settings for the Wi-Fi peripherals, i.e. Wi-Fi configurationsused in WPS*). *) Performing WPS between Dockee 100A and Wi-Fiperipheral 100E may require temporarily closing the Wi-Fi Directconnectivity link 120 towards Docking Station 100F. This would not benecessary in the NFC Connection Handover method. In some cases, IPconnectivity and change of Link layer network may require additionalbreaks.

In step 370, the Dockee device 100A receives the Wi-Fi connectivitysettings from the Docking station 100F over link 120. In step 372, theDockee device 100A may create Wi-Fi connections between itself andperipheral devices, for example the printer 100E, as has been prescribedby the received Wi-Fi connectivity settings.

During step 370, the Docking Station 100F may initiate the setup ofWi-Fi connections on the cases where it can perform it by itself, inaccordance with the Wi-Fi connectivity settings.

During step 370, the user may select peripherals, such as the printer100E, to be added into wireless docking environment. This may be merelyselecting peripherals from the Dockee 100A's user interface (whereperipherals are already known using Wi-Fi Direct Device Discovery andService Discovery features, and existing connectivity settings arevalid). Then the Dockee 100A may perform a WPS procedure for each Wi-Fiperipheral, using settings and instructions received from the DockingStation 100F. Each added peripheral needs to be reported to the DockingStation 100F with Smart Connectivity Setup Protocol messagesWDP_Peripheral_Info_Request/Response in respective steps 374 and 375.

When the user has completed adding more wireless peripherals, then SmartConnectivity Setup Protocol WDP_Complete_Request (and Response) may beexchanged by the Dockee 100A and the Docking Station 100F in respectivesteps 376 and 378.

After this, the Docking Station 100F may verify whether current Wi-Fisettings are still optimal, and make needed adjustments, if necessary.The Docking Station then completes defining the wireless dockingenvironment in step 380.

If some changes are made, then final Wi-Fi settings are exchanged withSmart Connectivity Setup Protocol WDP_Setup_(Request and) Response inrespective steps 382 and 384. However, it may be rare that Wi-Fisettings need to be changed in this phase.

The above example embodiment is merely one of many possible orders andmessage sequences that may be performed by the Wireless Docking Protocolusing network configuration program 144 information. Examples of thenetwork configuration program 144 include the Smart Connectivity SetupProtocol and the Universal Plug and Play (UPnP) Protocol.

Example Network Configuration Programs 144

Smart Connectivity Setup Protocol

In example embodiments of the invention, the step of defining theoptimal connections by the Docking Station 100F for one or more of thewireless devices in the wireless docking group, may use the SmartConnectivity Setup Protocol as its network configuration program 144.The Wireless Docking Protocol 142 illustrated in FIG. 3 and describedabove uses as its network configuration program 144, the SmartConnectivity Setup Protocol.

Smart Connectivity Setup Protocol is used to exchange data in definedformats and rules from the Dockee to the Docking Station so that theDocking Station is able to make optimal connectivity settings. And afterdefining these settings, Smart Connectivity Setup Protocol is used tocarry those settings and additional guidance from Docking Station toDockee. Additional guidance may include, for example, instructions toperform WPS with a specific peripheral.

The main goals of smart connectivity setup;

Enable optimal connectivity within wireless docking environment

Enable easy and consistent user experience

Smart connectivity setup has the following phases & tasks;

1) Gathering of capabilities of wireless devices and current wirelessconnectivity environments

2) Composing most optimal connectivity settings for wireless dockingwith minimum interference to non-wireless docking use cases, e.g. normalInternet connectivity.

3) Configuring Dockee, Docking Station and peripherals to use optimalconnectivity settings composed in step 2)

Smart connectivity setup is performed during initial setup of wirelessdocking environment, and when maintaining of wireless dockingenvironment requires connectivity changes.

Smart Connectivity Setup for Wi-Fi

1) Gathering Device Capabilities and Connectivity Environments

The purpose of this phase is to gather as much information as possibleto enable composition of optimal connectivity settings.

First Dock Configurator (Dockee) gathers information on known wirelessdevices and environments (=networks), e.g. configurations already storedinto Dock Configurator.

Then Dock Configurator should scan surrounding environment to searchother wireless devices and environments.

After gathering all possible information, the Dockee will send thisinformation to Dock Controller (Docking Station) by using WDP.

The information to be sent to Dock Controller includes;

a. The Wi-Fi Capabilities of the Dock Configurator Itself

Supported Wi-Fi modes; IBSS, P2P . . . .

Supported pairing mechanisms; WPS PBC, WPS PIN, WPS NFC, manual, . . . .

Maximum number of parallel networks (=number of implemented Wi-Fistacks)

Willingness to disconnect and change IP address

b. The Wi-Fi Capabilities of Each Known/Detected Devices which May bePotential Peripherals for the Wireless Docking Environment

Device identity

Device type [if known]

Supported Wi-Fi modes; IBSS, P2P . . . [If known]

Supported pairing mechanisms; WPS PBC, WPS PIN, WPS NFC, manual, . . .[If known]

Maximum number of parallel networks [If known]

Services provided [If known]

c. The Wi-Fi Status Per Each Available Connection of the Dockee

Connectivity status; attached, is able to connect, or is aware of thisnetwork

Network type; P2P, Infrastructure . . . .

Network SSID

Network Credentials [if allowed to share]

IP configuration; IP address, DHCP status, DNS etc. [if known]

d. Known Internet Connections

Interface/network

Information whether connection can be shared

2) Composing Optimal Connectivity Settings

Based on the information received within step 1), and possible with ownscanning of surrounding connectivity environment, the Dock Controllerdefines optimal connectivity architectures and methods for the wirelessdocking environment.

However, Dock Controller will take account that Dock Configurator(=device performing setup of wireless docking environment) may not bethe only user, i.e. the Dockee, for the wireless docking environment. Sothe environment will be applicable any Dockee that fulfills minimumrequirements of the Wireless Docking, see Section 4.

Also in exceptional cases Dock Controller may need to define separateconnectivity configurations;

Temporary connectivity configurations used only during the initial setupof the wireless docking environment. This may needed e.g. to enableconsistent user experience during initial setup despite of existingconnectivity configurations (e.g. Wi-Fi networks established already forother purposes than Wireless Docking)

Final connectivity configurations used during normal Wireless Dockingoperation.

3) Configuring Dockee, Docking Station and Peripherals

After defining the connectivity for the wireless docking environment,Dock Controller passes configurations to the Dock Configurator. AlsoDock Controller may send additional instructions, e.g. how to setupperipheral connectivity if direct connectivity between Dockee andperipheral is required. Based on received information and instructions,Dock Configurator configures itself, and also peripherals to be attachedwirelessly to the docking environment.

Standard WPS methods are used to configure peripherals.

Universal Plug and Play (UPnP) Protocol

In example embodiments of the invention, the step of defining theoptimal connections by the Docking Station 100F for one or more of thewireless devices in the wireless docking group, may use the UniversalPlug and Play (UPnP) Protocol as its network configuration program 144.Universal Plug and Play (UPnP) is a networking architecture thatprovides compatibility among networking equipment, software andperipherals of vendors who belong to the Universal Plug and Play Forum.UPnP was published as International Standard, ISO/IEC 29341, inDecember, 2008, incorporated herein by reference.

In an example embodiment of the invention, the Docking Station 100F, theDockee device 100A, and each peripheral device 100E and access point100B may include a UPnP capability. A UPnP compatible device from anyvendor may dynamically join a network, obtain an IP address, announceits name, and convey its capabilities upon request. A UPnP controlpoint, such as the Dockee Device 100A, is a control device that iscapable of discovering and controlling client devices, such as theprinter device and the access point, in a network through a programinterface, in an example embodiment of the invention.

The UPnP protocol includes the steps of discovery, description, control,event notification, and presentation. In an example embodiment of theinvention, after Wi-Fi Direct connection 120 is established between theDockee device 100A and the Docking Station 100F, the Dockee device 100Acollects from a peripheral device, such as the printer, the dynamicsettings and credentials of the peripheral device, which the Dockeedevice 100A then transmits to the Docking station 100F. The dynamicsettings and credentials may include an IP address of the peripheral andinformation on its type (i.e., a printer), its manufacturer, and itsmodel. In an example embodiment of the invention, the UPnP networkingdiscovery may be based on the printer's IP address returned by theDockee device 100A to the Docking Station 100F. Full device descriptionwith a UPnP format may obtained by using a URL address to the actuallocation of the printer's device, instead. When a device, such as theprinter peripheral device, is added to the network, the UPnP discoveryprotocol allows that device to advertise its services to control pointson the network, such as the Dockee device 100A, the Docking Station, andother peripheral devices. The exchange is a discovery message containingessential information about the device or one of its services, forexample, its type, identifier, and a pointer to more detailedinformation. The UPnP discovery protocol is based on the Simple ServiceDiscovery Protocol (SSDP).

In an example embodiment of the invention, the peripheral device mayadvertise its type (i.e., display, printer, mouse, keyboard, etc.) tothe control point, such as the Dockee device 100A. In an exampleembodiment of the invention, after the Dockee device 100A control pointhas discovered a peripheral device such as the printer, the Dockeedevice 100A may retrieve the device's description from a URL addressprovided by the peripheral device in the discovery message. For eachservice, the description includes a list of the commands, or actions, towhich the service responds. The peripheral may give a description of itscapabilities in a UPnP device discovery message to the Dockee device100A, including carrier type (i.e., Wi-Fi, Bluetooth), data raterequirements, message formats, and the like. The capabilities may alsobe obtained by the Dockee device 100A accessing a server on the Internetand doing a lookup using the peripheral device's manufacturer and modelnumber information as search keys. The Dockee device 100A then transmitsthe collected information to the Docking Station 100F.

An Example Application of the Wireless Docking Protocol

The following is an example application of the Wireless Docking Protocolsequence set forth in the sequence diagram of FIG. 3, to the exampleScenario 1 depicted in FIG. 2A:

First a normal WPS is performed to setup connectivity (Wi-Fi Directpreferred) over link 120 between Dockee 100A and Docking Station 100F,resulting in the Docking Station 100F becoming the peer-to-peer GroupOwner and the Dockee device 100A becoming the peer-to-peer client.

Then the Wireless Docking Protocol in the Dockee device 100A transfersthe gathered information over link 120 to the network configurationprogram 144 in the Docking Station 100F. In this example, the SmartConnectivity Setup Protocol is used as the network configuration program144.

Dockee 100A sends WDP_SCS_Request over link 120 to the Docking station100F, including the following information;

-   -   Wi-Fi capabilities;    -   Maximum number of parallel WLAN networks: 1    -   Supported Wi-Fi modes; <something>    -   Supported Wi-Fi features: <something>    -   Wi-Fi status (1):    -   Network SSID: <Infrastructure network>    -   Network type, configuration methods: <Infrastructure network        settings>    -   Status (attached, is able to connect, or is aware of this        network): is able to connect    -   Pairing mechanism: WPS (PBC, PIN, NFC), manual, other: <one of        these>    -   IP configuration (IP address, DHCP status, DNS, etc):        <something>    -   Internet connection (1):    -   Interface/network: network 1 (Infrastructure)    -   Status: inactive    -   Can be shared?: yes (Docking Station and peripherals may use        that internet connectivity if needed)    -   Other information like type etc: <something>    -   Willingness to disconnect and change IP address: yes (this value        is example, but recommended for single stack device. And        actually IP address has been released already when Wi-Fi Direct        connectivity performed towards Docking Station)    -   Wi-Fi peripheral (1):    -   Device type: Wi-Fi Printer    -   Device identification: <something>.    -   Used network and connectivity settings: network 1        (Infrastructure)

The Docking Station 100F defines the most optimal connectivity settingsbased on received information.

Important information is that Dockee 100A is single stack andInfrastructure network (the access point 100B) is available (which theDockee is able to use) and one peripheral (Wi-Fi printer) 100E isaccessible through that Infrastructure network. Also that Infrastructurenetwork is used for Internet connectivity.

Docking Station 100F defines the following settings and rules of theSmart Connectivity Setup Protocol for optimal connectivity in thewireless docking environment:

-   -   Dockee 100A may continue using new Wi-Fi Direct connection 120        (created in first phase).    -   Dockee 100A may access towards Internet through this Wi-Fi        Direct connection 120 (Dockee may retain current IP address as        long as Docking Station 100F acts as a bridge and not routing        traffic*) *) Dockee and/or Docking Station may also implement        Mobile IP to minimize effects of connectivity changes to the        Internet connectivity.    -   Peripheral Wi-Fi printer 100E may use current Infrastructure        connectivity settings over link 212, however see note below)    -   New peripherals may use new Wi-Fi Direct network (not any in        this scenario)

Then, Docking Station 100F joins to Wi-Fi AP (Infrastructure) over link214 using Credentials received from the Dockee 100A.

In this scenario the user does not add any unknown Wi-Fi peripherals,thus above Smart Connectivity Setup Protocol settings are final.

Note: There are various aspects which impact on the decision whether tokeep existing Infrastructure network links 210 and 212 or new Wi-FiDirect network link 120 for accessing Wi-Fi peripherals, such as printer100E.

1) Decision may be based on device type; i.e. how much bandwidth ittypically uses, what are delay constraints etc. This decision isbasically trade off between avoiding extra WPS procedure (=keep existingconnectivity) vs. shortening (=optimizing) route towards peripheral.

In this example scenario, it is assumed that Docking Station 100F keepsthe current Wi-Fi printer connectivity link 212 and thus no ‘extra’ WPSis required towards printer 100E.

2) User decides what peripherals are added to wireless dockingenvironment, and using WPS just for selecting Wi-Fi peripherals is oneoption.

Scenario [1′]—Dual Stack Dockee with TDLS and Wi-Fi Direct with ExistingInfrastructure Network

FIG. 1B is an example embodiment of a Dockee device 100A′ comprising aWLAN communications protocol stack 203 and a Tunneled Direct Link Setupcommunications protocol stack 204 and an example wireless DockingStation device 100F comprising a WLAN communications protocol stack 203′and a Tunneled Direct Link Setup communications protocol stack 204′,performing the Wireless Docking Protocol 142 procedure over a TunneledDirect Link Setup communication connection 120′, according to anembodiment of the present invention.

FIG. 2B is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi infrastructure networkconfiguration of a mobile phone 100A′ of FIG. 1B, having a dual protocolstack supporting TDLS and Infrastructure operation modes, with a WLANcommunications protocol stack 203 and a Tunneled Direct Link Setupcommunications protocol stack 204, connected as a client over link 210to an access point 100B, and a single stack printer 100E that supportsWi-Fi Protected setup, which is also connected over link 212 to theaccess point 100B, the transformation creating a wireless dockingenvironment by means of a Docking Station 100F of FIG. 1B, having a dualprotocol stack supporting TDLS and Infrastructure operation modes, witha WLAN communications protocol stack 203′ and one Tunneled Direct LinkSetup communications protocol stack 204′, performing the WirelessDocking Protocol 142 procedure with the Dockee device 100A to create thewireless docking environment, with the mobile phone 100A′ in the role ofa Dockee connected over the link 120′ to the Docking Station 100F, theprinter 100E as a peripheral connected over the existing link 212, andthe access point 100B connected over the link 214 to the Docking Station100F providing Wi-Fi connectivity in the environment, according to anembodiment of the present invention.

In the example embodiment of FIG. 2B, instead of creating a Wi-Fi Directlink between Dockee and Docking Station, a Tunneled Direct Link Setup(TDLS) link 120′ is created to enable direct data path between thedevices. This direct data path may be needed in wireless display andsuch technologies.

However, to be able use TDLS both Infrastructure client devices (Dockee)and (Docking Station) need to support TDLS feature (TDLS is transparentto AP and no specific support needed in AP). TDLS may be used by singlestack devices, but TDLS requires own channel for TDLS link. So devicessupporting TDLS are dual channel capable and thus the simplest Dockeedevices do not support TDLS. In general TDLS may considered as anoptional feature in case of Wireless Docking.

If both Dockee and Docking Station support TDLS, Docking Station mayprefer to use TDLS instead of Wi-Fi Direct.

In the sequence diagram of FIG. 3, the Initial Setup may be a Wi-FiProtected Setup (WPS) procedure between Dockee and Docking Station,establishing a Wi-Fi Direct link. But this Wi-Fi Direct link would beonly a temporary connection used during initial setup. Finalconnectivity settings would then use Infrastructure and TDLS.

The Docking Station defines the following settings and rules for SmartConnectivity Setup Protocol for optimal connectivity in the wirelessdocking environment:

-   -   Dockee uses existing Infrastructure connection with TDLS.    -   Dockee accesses towards Internet through Infrastructure        connection    -   Peripheral Wi-Fi printer uses current Infrastructure        connectivity settings    -   New peripherals uses new Infrastructure network (not any in this        scenario)

These settings are used after completion of initial setup, i.e. afterWDP_Setup_Response message. The Dockee and Docking Station terminatetemporary Wi-Fi Direct link and start to use Infrastructure connectionwith direct TDLS link (actual TDLS link setup is done throughInfrastructure connection as specified in TDLS specification).

When using Infrastructure with TDLS, all of the Wi-Fi peripherals shouldalso use Infrastructure network.

Scenario [2]—Dual Stack Dockee with Wi-Fi Direct with ExistingInfrastructure Network

FIG. 1C is an example embodiment of a Dockee device 100A″ comprising adual Wi-Fi communications protocol stack operating in Wi-Fi Direct andInfrastructure modes 202 and 203 and an example wireless Docking Stationdevice 100F comprising a dual Wi-Fi communications protocol stackoperating in Wi-Fi Direct and Infrastructure modes 202′ and 203′,performing the Wireless Docking Protocol 142 procedure over a Wi-FiDirect communication connection 120″, according to an embodiment of thepresent invention.

FIG. 2C is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi infrastructure networkconfiguration of a mobile phone 100A″ of FIG. 1C, having a dual Wi-Ficommunications protocol stack supporting Wi-Fi Direct and Infrastructureoperation modes, connected as a client over link 210 to an access point100B, and a single stack printer 100E that supports Wi-Fi Protectedsetup, which is also connected over link 212 to the access point 100B,the transformation creating a wireless docking environment by means of aDocking Station 100F of FIG. 1C, having a dual Wi-Fi communicationsprotocol stack supporting Wi-Fi Direct and Infrastructure operationmodes, performing the Wireless Docking Protocol 142 procedure with theDockee 100A″ to create the wireless docking environment, with the mobilephone 100A″ in the role of a Dockee connected over connection 120″ tothe Docking station 100F, the printer 100E as a peripheral connectedover link 212 to the access point 100B, the Docking Station 100Fconnected over link 214 to the access point 100B, and the access point100B providing Wi-Fi connectivity in the environment, according to anembodiment of the present invention.

Assumptions for the Scenario 2:

Mobile phone is dual stack device, and printer is single stack device.

Mobile phone is used to setup wireless docking environment.

In initial state of FIG. 3, the user has created an Infrastructurenetwork with two client devices; mobile phone and printer using two WPSprocedures;

-   -   Between a mobile phone and an AP    -   Between a printer and an AP.

Then user buys Docking Station 100F to create wireless dockingenvironment, and user wants to use existing mobile phone 100A″, printer100E and AP 100B for that environment.

Like in scenario 1, direct Wi-Fi link between Dockee and Docking Stationis preferred, thus Wi-Fi Direct should be used between those.

However, in this case, mobile phone could keep existing Infrastructureconnection towards AP (e.g. Internet connectivity) due dual stackimplementation, and actually it is preferred because Internetconnectivity would not steal bandwidth from Wi-Fi Direct link, and alsodelays are shorter (no routing via Docking Station).

So in this case, the most optimal solution would be just to createadditional Wi-Fi Direct link towards Docking Station as shown in lowerpart of FIG. 6 shows optimal Wi-Fi connectivity after creating wirelessdocking environment.

But, as said in Scenario 1, this dual connectivity support may not bevisible to user, and connectivity setup for wireless docking environmentshould work same way.

However, Docking Station may be capable to serve also single stackDockees, thus if Internet connectivity or access to certain Wi-Fiperipheral (that is connected to the AP) is needed for such Dockee, thenDocking Station may be able to create Wi-Fi Infrastructure connectionbetween itself and the AP.

Note: If Docking Station would require Internet connectivity by itself,then Infrastructure connection could be created between Docking Stationand AP. However, if using traditional method, yet another WPS would berequired.

The following is an example application of the Wireless Docking Protocolsequence set forth in the sequence diagram of FIG. 3, to the exampleScenario 2 depicted in FIG. 2C:

First a normal WPS is performed to setup connectivity (Wi-Fi Directpreferred) over link 120″ between Dockee 100A″ and Docking Station 100F,resulting in the Docking Station 100F becoming the peer-to-peer GroupOwner and the Dockee device 100A″ becoming the peer-to-peer client.

Then the Wireless Docking Protocol transfers the network configurationprogram 144 information over link 120″ from the Dockee device 100A″ tothe Docking Station 100F. In this example, the Smart Connectivity SetupProtocol is used as the network configuration program 144.

Dockee 100A″ sends WDP_SCS_Request over link 120″ to Docking station100F, including the following information;

-   -   Wi-Fi capabilities;    -   Maximum number of parallel WLAN networks: 2    -   Supported Wi-Fi modes; <something>    -   Supported Wi-Fi features: <something>    -   Wi-Fi status (1):    -   Network SSID: <Infrastructure network>    -   Network type, configuration methods: <Infrastructure network        settings>    -   Status (attached, is able to connect, or is aware of this        network): attached    -   Pairing mechanism: WPS (PBC, PIN, NFC), manual, other: <one of        these>    -   IP configuration (IP address, DHCP status, DNS, etc):        <something>    -   Internet connection (1):    -   Interface/network: network 1 (Infrastructure)    -   Status: active    -   Can be shared?: yes    -   Other information like type etc: <something>    -   Willingness to disconnect and change IP address: no (just        example; in dual stack case this value would not typically have        any impact)    -   Wi-Fi peripheral (1):    -   Device type: Wi-Fi Printer    -   Device identification: <something>.    -   Used network and connectivity settings: network 1        (Infrastructure)

Docking Station defines most optimal connectivity settings based onreceived information.

Important information is that Dockee 100A″ is dual stack andInfrastructure network is available and used by the Dockee andperipheral (Wi-Fi printer 100E). Also that Infrastructure network isused for Internet connectivity.

Docking Station 100F defines the following settings and rules fornetwork configuration program 144 for optimal connectivity in thewireless docking environment:

-   -   Dockee 100A″ may use new Wi-Fi Direct connection 120″ only for        accessing peripherals attached directly to Docking Station (e.g.        remote display, USB devices etc.)    -   Dockee 100A″ may continue accessing Internet by using existing        Infrastructure connection 210.    -   Peripheral Wi-Fi printer 100E may use current Infrastructure        connectivity settings over link 212 (no need to perform WPS for        reconfiguring Wi-Fi printer)    -   New peripherals may use new Wi-Fi Direct network (not any in        this scenario)

Note: Docking Station 100F joins to Wi-Fi AP (Infrastructure) usingCredentials received from the Dockee only when some another single stackDockee starts to use docking environment, or when Docking Station byitself needs Internet connectivity.

In this scenario user does not add any unknown Wi-Fi peripherals, thusabove network configuration program 144 settings are also final ones.

FIG. 1D is an example embodiment of the Dockee device 100A″ of FIG. 1C,comprising an example dual radio embodiment with the dual Wi-Ficommunications protocol stack 202 and 203. The protocol stack 202operates in Wi-Fi Direct mode and in example embodiments, may includeWi-Fi Direct upper layer protocols, Wi-Fi Direct logical link layer, andWi-Fi Direct MAC sublayer. The protocol stack 203 operates inInfrastructure mode and in example embodiments, may include WLAN upperlayer protocols, WLAN logical link layer, and WLAN MAC sublayer. Eachprotocol stack 202 or 203 may have its respective digital basebandtransmission path outputting its signal to the respective radio 170 or180. On the receive side, the respective radio 170 or 180 outputs thereceived signal to the digital baseband transmission path of therespective protocol stack 202 or 203, according to an embodiment of thepresent invention.

The example Wi-Fi Direct protocol stack 202 in example embodiments, mayhave the digital baseband transmission path of the Wi-Fi MAC sublayeroutput the digital baseband signal through physical layer (PHY) logic toa digital-to-analog converter and transmitter of an example RF radio180. The modulated output of the RF radio 180 may be amplified by apower amplifier and applied to a transmit/receive switch and the antennaof the Wi-Fi Direct link. In receiving signals on the antenna of theWi-Fi Direct link, the transmit/receive switch passes the RF signal tothe receiver of the RF radio 180 and an analog-to-digital converter. Thedemodulated digital baseband signal then passes through PHY layer logicto the Wi-Fi Direct MAC sublayer of the Wi-Fi Direct protocol stack 202.

The example WLAN protocol stack 203 in example embodiments, may have thedigital baseband transmission path of the WLAN MAC sublayer output thedigital baseband signal through physical layer (PHY) logic to adigital-to-analog converter and transmitter of an example RF radio 170.The modulated output of the RF radio 170 may be amplified by a poweramplifier and applied to a transmit/receive switch and the antenna ofthe WLAN link. In receiving signals on the antenna of the WLAN link, thetransmit/receive switch passes the RF signal to the receiver of the RFradio 170 and an analog-to-digital converter. The demodulated digitalbaseband signal then passes through PHY layer logic to the WLAN MACsublayer of the WLAN protocol stack 203.

Scenario [3]—Single Stack Dockee with Wi-Fi Direct with Existing Wi-FiDirect Network

FIG. 2D is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi network configuration of a mobilephone 100A of FIG. 1A, having a single Wi-Fi stack supporting Wi-FiDirect and Infrastructure operation modes, connected over link 216 to asingle stack printer that supports Wi-Fi Direct, the transformationcreating a wireless docking environment by means of a Docking Station100F of FIG. 1A, having a dual Wi-Fi stack supporting Wi-Fi Direct andInfrastructure operation modes, performing the Wireless Docking Protocol142 procedure with the Dockee device 100A to create the wireless dockingenvironment, with the mobile phone 100A in the role of a Dockeeconnected over link 120 to the Docking Station 100F, the printer 100E asa peripheral connected over link 218 to the Docking Station 100F, andthe Docking Station 100F providing Wi-Fi connectivity in theenvironment, according to an embodiment of the present invention.

Assumptions for the Scenario:

Both clients (mobile phone and printer) are single stack devices.However, there is no AP available.

Mobile phone is used to setup wireless docking environment.

In initial state of FIG. 2D user has created Wi-Fi Direct connectivityover link 216 between mobile phone 100A and printer 100E; either

-   -   Temporary Wi-Fi Direct connection created by WPS (a new        peer-to-peer (P2P) network created every time when needed)    -   Persistent Wi-Fi Direct connection created by WPS (“always        available” P2P network—WPS needed only the first time)

Either of those devices 100A and 100E becomes Group Owner (GO) of theWi-Fi Direct network (which one is not relevant on this case, mobilephone being P2P GO is just an example)

Then user buys Docking Station 100F to create wireless dockingenvironment, and user wants to use existing mobile phone 100A andprinter 100E for that environment.

But, adding a Docking Station as a new P2P client is not optimal,because Docking Station would typically serve multiple Dockees. DockingStation is a ‘non-mobile, always on’ device, thus it would be muchbetter that Docking Station acts as a P2P GO. Also Docking Station mayprovide Internet connectivity through Ethernet, thus it would be betterthat central device of the Wi-Fi Direct network provides Internetconnectivity.

Note, that a peer-to-peer Group Owner (P2P GO) is basically an AP withadditional capabilities.

Thus, in this case, the most optimal solution may be to create a newWi-Fi Direct network where Docking Station acts as a P2P GP as shown onthe right side of FIG. 2D, after creating a wireless dockingenvironment.

The following is an example application of the Wireless Docking Protocolsequence set forth in the sequence diagram of FIG. 3, to the examplescenario depicted in FIG. 2D:

First normal WPS link is formed to setup connectivity (Wi-Fi Directpreferred) over link 120 between Dockee 100A and Docking Station 100F,resulting in the Docking Station 100F becoming the peer-to-peer GroupOwner and the Dockee device 100A becoming the peer-to-peer client.

Then, the Wireless Docking Protocol transfers the network configurationprogram 144 information from the Dockee device 100A to the DockingStation 100F. In this example, the Smart Connectivity Setup Protocol isused as the network configuration program 144.

Dockee 100A sends WDP_SCS_Request over link 120 to Docking station 100F,including the following information;

-   -   Wi-Fi capabilities;    -   Maximum number of parallel WLAN networks: 1    -   Supported Wi-Fi modes; <something>    -   Supported Wi-Fi features: <something>    -   Wi-Fi status (1):    -   Network SSID: <Wi-Fi Direct network towards printer>    -   Network type, configuration methods: <Wi-Fi Direct network        settings>    -   Status (attached, is able to connect, or is aware of this        network): is able to connect    -   Pairing mechanism: WPS (PBC, PIN, NFC), manual, other: <one of        these>    -   IP configuration (IP address, DHCP status, DNS, etc):        <something>    -   Internet connection (n/a):    -   Willingness to disconnect and change IP address: n/a    -   Wi-Fi peripheral (1):    -   Device type: Wi-Fi Printer    -   Device identification: <something>.    -   Used network and connectivity settings: network 1 (Wi-Fi Direct)

Docking Station 100F defines most optimal connectivity settings based onreceived information.

Important information is that Dockee 100A is single stack and Wi-FiDirect network link 120 is available (Dockee is able to use that) andone peripheral (Wi-Fi printer 100E) is accessible through that networklink 120.

However, in this scenario this original Wi-Fi Direct network 216 is notoptimal anymore, thus Docking Station 100F creates new Wi-Fi Directnetwork 218.

Docking Station 100F defines the following settings and rules fornetwork configuration program 144 for optimal connectivity in thewireless docking environment:

-   -   Dockee 100A may continue using new Wi-Fi Direct connection 120        (created in first phase).    -   Dockee 100A may access Internet by using new Wi-Fi Direct        connection 120 (if can be provided by the Docking Station 100F).    -   Peripheral Wi-Fi printer 100E connectivity settings 216 are not        valid anymore (new WPS procedure*) may be performed to        reconfigure Wi-Fi printer 100E if that printer is wanted to be a        peripheral within docking environment. Dockee gives necessary        guidance to user via UI to perform WPS procedure. *) Preferred        solution is that Dockee performs WPS on behalf of Docking        Station, i.e. WPS is performed between Dockee and peripheral,        but using Wi-Fi settings received from Docking Station. Also in        this WPS procedure it may be ensured that peripheral uses        Docking Station as peer-to-peer Group Owner (P2P GO). This may        require adjusting some identities in WPS procedure. As a        secondary alternative, a normal WPS link 218 may be performed        directly between peripheral 100E and Docking Station 100F.    -   New peripherals may use new Wi-Fi Direct network (not any in        this scenario)

In this scenario, the user does not add any unknown Wi-Fi peripherals,thus the above network configuration program 144 settings are also finalones.

Scenario [4]—Dual Stack Dockee with Wi-Fi Direct with Existing Wi-FiDirect and Infrastructure Networks

FIG. 2E is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi infrastructure networkconfiguration of a mobile phone having a dual Wi-Fi communicationsprotocol stack supporting Wi-Fi Direct and Infrastructure operationmodes, connected as a client to an access point, connected to a singlestack printer that supports Wi-Fi Direct, the transformation creating awireless docking environment by means of a Docking Station having a dualWi-Fi communications protocol stack supporting Wi-Fi Direct andInfrastructure operation modes, performing a wireless docking procedureto create the wireless docking environment, with the mobile phone in therole of a Dockee, the printer as a peripheral, and the access pointproviding Wi-Fi connectivity in the environment, according to anembodiment of the present invention.

FIG. 2E is a wireless network diagram of an example embodiment, showinga transformation of an existing Wi-Fi infrastructure networkconfiguration of a mobile phone 100A″ of FIG. 1C, having a dual Wi-Ficommunications protocol stack supporting Wi-Fi Direct and Infrastructureoperation modes, connected as a client to an access point 100B, andconnected to a single stack printer 100E that supports Wi-Fi Direct, thetransformation creating a wireless docking environment by means of aDocking Station 100F of FIG. 1C, having a dual Wi-Fi communicationsprotocol stack supporting Wi-Fi Direct and Infrastructure operationmodes, performing the Wireless Docking Protocol 142 procedure with theDockee 100A″ to create the wireless docking environment, with the mobilephone 100A″ in the role of a Dockee connected over link 120″ to theDocking Station 100F, the printer 100E as a peripheral connected overlink 224 to the Docking Station 100F, the Dockee 100A″ connected overlink 226 to the access point 100B and the access point 100B providingWi-Fi connectivity in the environment, according to an embodiment of thepresent invention.

Assumptions for the Scenario:

Mobile phone is dual stack device, and printer is single stack device.

In the initial state, the user has created both Wi-Fi Direct andInfrastructure networks requiring two WPS procedures;

-   -   Between a mobile phone and an AP to setup Infrastructure        connectivity    -   Between a printer and mobile phone to setup Wi-Fi Direct        connectivity.

Even if mobile phone is dual stack device, both stacks are alreadyreserved. However, due reasons described in scenario 3, existing Wi-FiDirect network is not optimal, and thus a new Wi-Fi Direct network whereDocking Station is P2P GO should be created.

But, using existing WPS methods, needed actions to setup such Wi-FiDirect network is not very obvious for the user. Making WPS betweenDockee and Docking Station could be quite obvious, but how user noticesto create WPS between printer and Docking Station (printer had alreadyworking connectivity). Most obvious method would be device informinguser that connection to printer will be broken.

Note: End result as shown in scenario 2 is as well applicable.

However, Docking Station may be capable to serve also single stackDockees, thus if Internet connectivity is needed for such Dockee, thenDocking Station may be able to create Wi-Fi Infrastructure connectionbetween itself and the AP.

Note: If Docking Station would require Internet connectivity by itself,then Infrastructure connection could be created between Docking Stationand AP. However, if using traditional method, yet another WPS isrequired.

The following is an example application of the Wireless Docking Protocolsequence set forth in the sequence diagram of FIG. 3, to the examplescenario depicted in FIG. 2E:

First is performed normal WPS to setup connectivity (Wi-Fi Directpreferred) over link 120″ between Dockee 100A″ and Docking Station 100F,resulting in the Docking Station 100F becoming the peer-to-peer GroupOwner and the Dockee device 100A″ becoming the peer-to-peer client.

Then the Wireless Docking Protocol transfers the network configurationprogram 144 information from the Dockee device 100A″ to the DockingStation 100F. In this example, the Smart Connectivity Setup Protocol isused as the network configuration program 144.

Dockee 100A″ sends WDP_SCS_Request to the Docking Station 100F,including the following information;

-   -   Wi-Fi capabilities;    -   Maximum number of parallel WLAN networks: 2    -   Supported Wi-Fi modes; <something>    -   Supported Wi-Fi features: <something>    -   Wi-Fi status (1):    -   Network SSID: <Infrastructure network>    -   Network type, configuration methods: <Infrastructure network        settings>    -   Status (attached, is able to connect, or is aware of this        network): attached    -   Pairing mechanism: WPS (PBC, PIN, NFC), manual, other: <one of        these>    -   IP configuration (IP address, DHCP status, DNS, etc):        <something>    -   Wi-Fi status (2):    -   Network SSID: <Wi-Fi Direct network>    -   Network type, configuration methods: <Wi-Fi Direct network        settings>    -   Status (attached, is able to connect, or is aware of this        network): is able to connect    -   Pairing mechanism: WPS (PBC, PIN, NFC), manual, other: <one of        these>    -   IP configuration (IP address, DHCP status, DNS, etc):        <something>    -   Internet connection (1):    -   Interface/network: network 1 (Infrastructure)    -   Status: active    -   Can be shared?: yes    -   Other information like type etc: <something>    -   Willingness to disconnect and change IP address: no (just        example; in dual stack case this value would not typically have        any impact)    -   Wi-Fi peripheral (1):    -   Device type: Wi-Fi Printer    -   Device identification: <something>.    -   Used network and connectivity settings: network 2 (Wi-Fi Direct)

Docking Station 100F defines most optimal connectivity settings based onreceived information.

Important information is that Dockee 100A″ is dual stack and twodifferent networks are used. Infrastructure network with access point100B is used for Internet connectivity.

Docking Station defines the following settings and rules for networkconfiguration program 144 for optimal connectivity in the wirelessdocking environment:

-   -   Dockee 100A″ may use new Wi-Fi Direct connection 120″ only for        accessing peripherals attached directly to Docking Station 100F        (e.g. remote display, USB devices etc.). Also Wi-Fi printer 100E        would be attached directly over link 224 to Docking Station 100F        in this case.    -   Dockee 100A″ may continue accessing Internet by using existing        Infrastructure connection over link 226 to the access point        100B.    -   Peripheral Wi-Fi printer 100E connectivity settings 220 are not        valid anymore (new WPS procedure) may be performed to        reconfigure Wi-Fi printer 100E if that printer is wanted to be a        peripheral within docking environment. Dockee 100A″ gives        necessary guidance to user via UI to perform WPS procedure.    -   New peripherals may use new Wi-Fi Direct network (not any in        this scenario)

Note: Docking Station 100F joins to Wi-Fi AP (Infrastructure) usingCredentials received from the Dockee 100A″ only when some another singlestack Dockee starts to use docking environment, or when Docking Stationby itself needs Internet connectivity.

In this scenario user does not add any unknown Wi-Fi peripherals, thusabove network configuration program 144 settings are also final ones.

Scenario [5]—Single Stack Dockee with Wi-Fi Direct Creating New DockingEnvironment

FIG. 2F is a wireless network diagram of an example embodiment, showingthe creation of a wireless docking environment by means of a DockingStation 100F of FIG. 1A, having a dual Wi-Fi stack supporting Wi-FiDirect and Infrastructure operation modes, performing the WirelessDocking Protocol 142 procedure with dockee device 100A to create thewireless docking environment that includes a mobile phone 100A of FIG.1A, having a single Wi-Fi stack supporting Wi-Fi Direct andInfrastructure operation modes, which assumes the role of a Dockee, themobile phone/Dockee 100A forwarding a user indication over link 120 tothe Docking Station 100F that a single stack printer 100E that supportsWi-Fi Direct is to be included in the wireless docking environment, theDocking Station 100F providing Wi-Fi connectivity in the environment,according to an embodiment of the present invention.

The Docking Station 100F uses the Wireless Docking Protocol to transferthe network configuration program 144 information from the Dockee device100A to setup a completely new Wi-Fi connectivity by using only Wi-FiDirect network. Dockee 100A is single stack device.

User has mobile phone (Dockee) 100A, Wi-Fi printer 100E and DockingStation 100F, but there are no prior Wi-Fi configurations.

The setup starts in step 1 with creation of Wi-Fi Direct network 120between Dockee 100A and Docking Station 100F (as in other scenarios).

Then Dockee 100A may forward information on its Wi-Fi capabilities andstatus. However, Wi-Fi status in this case would be very limited.

Dockee 100A sends WDP_SCS_Request to the Docking Station 100F in step 2,including the following information;

-   -   Wi-Fi capabilities;    -   Maximum number of parallel WLAN networks: 1    -   Supported Wi-Fi modes; <something>    -   Wi-Fi status (n/a):    -   Internet connection (n/a):    -   Willingness to disconnect and change IP address: n/a    -   Wi-Fi peripheral (n/a):

Docking Station 100F defines most optimal connectivity settings based onreceived information;

Important information is that Dockee 100A is single stack device. But inthis case Docking Station 100F does not have any information about otherWi-Fi networks, thus Docking Station 100F issues commands to use thenewly created Wi-Fi Direct network 120 for everything:

-   -   Dockee 100A may continue using the new Wi-Fi Direct connection        120 (created in first phase).    -   Dockee 100A may access Internet by using new Wi-Fi Direct        connection 120 (if it can be provided by the Docking Station        100F).    -   New peripherals may use new Wi-Fi Direct network 120.

The Docking Station 100F also commands the Dockee 100A to perform a newWPS in step 3 towards the peripherals (e.g., printer 100E), since theperipherals need the Credentials of the new Wi-Fi Direct network. Dockee100A then may perform WPS towards peripherals by using WPS (any methodavailable on the peripheral) in step 3, see details e.g. from scenario3. Dockee 100A may perform this WPS on behalf of Docking Station 100F*)to create Wi-Fi Direct link 230 in step 4. Dockee 100A gives necessaryguidance to user via user interface UI to perform these WPS procedures.*) This is similar to WPS External Registrar concept.

In this scenario user adds a new Wi-Fi peripheral (printer 100E), butstill earlier defined network configuration program 144 settings areoptimal and thus the final ones.

Scenario [6]—Dual Stack Dockee with Wi-Fi Direct Creating New DockingEnvironment

FIG. 2G is a wireless network diagram of an example embodiment, showingthe creation of a wireless docking environment by means of a DockingStation 100F of FIG. 1C, having a dual Wi-Fi stack supporting Wi-FiDirect and Infrastructure operation modes, performing the WirelessDocking Protocol 142 procedure with the Dockee device 100A″ to createthe wireless docking environment that includes a mobile phone 100A″ ofFIG. 1C, having a dual Wi-Fi communications protocol stack supportingWi-Fi Direct and Infrastructure operation modes, connected over link 234as a client to an access point 100B, the mobile phone 100A″ assuming therole of a Dockee, the mobile phone/Dockee 100A″ forwarding a userindication to the Docking Station 100F over link 120 that a single stackprinter 100E that supports Wi-Fi Direct is to be included in thewireless docking environment, the mobile phone/Dockee 100A″ providingWi-Fi connectivity in the environment, according to an embodiment of thepresent invention.

The Docking Station 100F uses the Wireless Docking Protocol 142 totransfer the network configuration program 144 information from theDockee device 100A″ to setup a completely new Wi-Fi connectivity byusing only Wi-Fi Direct network. Dockee 100A″ is dual stack device.

User has mobile phone (Dockee) 100A″, Wi-Fi printer 100E, Wi-Fi AP 100Band Docking Station 100F, but there are no prior Wi-Fi configurations.

Note: Also Wi-Fi AP 100B is assumed to be ‘legacy’ device and standardWPS may be used towards AP 100B.

The setup starts with creation in step 1 of Wi-Fi Direct network link120″ between Dockee 100A″ and Docking Station 100F (as in otherscenarios).

Then Dockee 100A″ may forward information on its Wi-Fi capabilities andstatus in step 2 to the Docking Station 100F. However, Wi-Fi status inthis case would be very limited.

Dockee 100A″ sends WDP_SCS_Request over link 120″ to the Docking Station100F, including the following information;

-   -   Wi-Fi capabilities;    -   Maximum number of parallel WLAN networks: 2    -   Supported Wi-Fi modes; <something>    -   Wi-Fi status (n/a):    -   Internet connection (n/a):    -   Willingness to disconnect and change IP address: n/a    -   Wi-Fi peripheral (n/a):

Docking Station 100F defines the most optimal connectivity settingsbased on the received information. Important information is that Dockee100A″ is a dual stack device. But in this case Docking Station 100F doesnot have any information about other Wi-Fi networks*), thus DockingStation 100F issues commands to use the newly created Wi-Fi Directnetwork link 120″ for everything: *) Docking Station 100F is not awareof Infrastructure network access point 100B or at least does not havecredentials of the Infrastructure network, thus it cannot use thatnetwork. However, if either Dockee 100A″ or Docking Station 100F hasdetected this Infrastructure network access point 100B by the scanning,then Docking Station 100F may give some guidance to user, e.g. toperform WPS towards AP 100B within WDP_SCS_Response.

-   -   Dockee 100A″ may continue using new Wi-Fi Direct connection 120″        (created in first phase).    -   Dockee 100A″ may access Internet by using new Wi-Fi Direct        connection 120″ and infrastructure link 236 (if it can be        provided by the Docking Station 100F).    -   New peripherals may use new Wi-Fi Direct network 120″.

If the user has performed WPS in step 3 between Dockee 100A and AP 100B,the Dockee should report this to the Docking Station 100F (e.g. withinWDP_Complete_Request).

Then Docking Station 100F checks whether initial configurations wereoptimal (=created Wi-Fi Direct network).

But, in this scenario, only Wi-Fi AP 100B provides InternetConnectivity, thus the Infrastructure network link 234 may be also beused for wireless docking environment. So Docking Station 100F may needto define new rules for network configuration program 144. New settingsmay be sent within WDP_Setup_Response to the Dockee:

-   -   Dockee may use new Wi-Fi Direct connection 120″ for accessing        peripherals, e.g. printer 100E, attached directly to Docking        Station 100F (e.g. remote display, USB devices etc.). Also Wi-Fi        printer 100E may be attached directly to Docking Station 100F in        this case.    -   Dockee 100A″ may access Internet by using new Infrastructure        connection 234.

FIG. 4, is an example flow diagram 400 of operational steps of anexample embodiment of the method carried out by the Docking Station 100Fin performing the Wireless Docking Protocol 142 to form a wirelessdocking environment. The steps of the flow diagram 400 representcomputer code instructions stored in the RAM and/or ROM memory of theDocking Station device 100F, which when executed by the centralprocessing units (CPU), carry out the functions of the exampleembodiments of the invention. The steps may be carried out in anotherorder than shown and individual steps may be combined or separated intocomponent steps. Additional steps may be inserted into this sequence.The steps of the example method are as follows.

Step 402: forming a communication link between a wireless dockingstation and a dockee device;

Step 404: receiving, by the Docking Station, from the Dockee device,information about the Dockee device's capabilities and characteristicsof one or more wireless devices within a wireless docking group;

Step 406: defining, by the Docking Station, one or more optimalconnections for one or more of the wireless devices in the wirelessdocking group, based on the received information; and

Step 408: transmitting, by the Docking Station, to the Dockee device,information to enable formation of the one or more optimal connectionsfor the one or more devices in the wireless docking group.

FIGS. 5A to 5E are, collectively, an example flow diagram 500 ofoperational steps of an example embodiment of the Wireless DockingProtocol 142 procedure in the Docking Station 100F, to define the Wi-Ficonnectivity settings for a peripheral printer 100E, using the networkconfiguration program 144, according to an embodiment of the presentinvention. The steps of the flow diagram 500 represent computer codeinstructions stored in the RAM and/or ROM memory of the Docking Stationdevice 100F, which when executed by the central processing units (CPU),carry out the functions of the example embodiments of the invention. Thesteps may be carried out in another order than shown and individualsteps may be combined or separated into component steps. Additionalsteps may be inserted into this sequence. The steps of the examplemethod are as follows.

FIG. 5A continues the Wireless Docking Protocol 142 procedure of FIG. 4,showing Step 404: receiving the Dockee device's capabilities andcharacteristics of wireless devices within a wireless docking group andStep 406: defining optimal connections. Step 502 determines whether theDockee 100A has a single protocol stack on path 502A or a dual protocolstack on path 502B. Path 502A passes to step 504 that determines whetherthe plan is to add Docking Station 100F to an existing network on path504A or form new network with Docking Station 100F on path 504B. Path504A passes to the flow diagram of FIG. 5B and Path 504B passes to theflow diagram of FIG. 5C. Path 502B passes to step 506 that determineswhether the plan is to add Docking Station 100F to an existing networkon path 506A or form new network with Docking Station 100F on path 506B.Path 506A passes to the flow diagram of FIG. 5D and Path 506B passes tothe flow diagram of FIG. 5E.

FIG. 5B continues the Wireless Docking Protocol 142 procedure of FIG.5A, where the Dockee 100A has a single protocol stack and a DockingStation 100F is to be added to an existing network.

Step 508 determines whether there is an existing internet access point100B on path 508A or there is no existing internet connection on path508B. Path 508A, there is an existing internet access point 100B, passesto step 510 that determines on path 510A whether the peripheral printer100E is connected to access point 100B (Scenario 1 of FIG. 2A) or onpath 510B whether the peripheral printer 100E is connected to Dockee100A (Scenario 3 of FIG. 2D).

If the peripheral printer 100E is connected to access point 100B(Scenario 1 of FIG. 2A) on path 510A, then the Wireless Docking Protocol142 procedure passes the gathered information received from the Dockeedevice 100A to the Smart Connectivity Setup Protocol subroutine that isused as the network configuration program 144 in this example.

For (Scenario 1 of FIG. 2A) on path 510A, the Docking Station 100Fdefines the most optimal connectivity settings based on receivedinformation.

Important information is that Dockee 100A is single stack andInfrastructure network (the access point 100B) is available (which theDockee is able to use) and one peripheral (Wi-Fi printer) 100E isaccessible through that Infrastructure network. Also that Infrastructurenetwork is used for Internet connectivity.

Docking Station 100F defines the following settings and rules of theSmart Connectivity Setup Protocol for optimal connectivity in thewireless docking environment:

-   -   Dockee 100A may continue using new Wi-Fi Direct connection 120        (created in first phase).    -   Dockee 100A may access towards Internet through this Wi-Fi        Direct connection 120 (Dockee may retain current IP address as        long as Docking Station 100F acts as a bridge and not routing        traffic*) *) Dockee and/or Docking Station may also implement        Mobile IP to minimize effects of connectivity changes to the        Internet connectivity.    -   Peripheral Wi-Fi printer 100E may use current Infrastructure        connectivity settings over link 212, however see note below)    -   New peripherals may use new Wi-Fi Direct network (not any in        this scenario)

Then, Docking Station 100F joins to Wi-Fi AP (Infrastructure) over link214 using Credentials received from the Dockee 100A.

In this scenario the user does not add any unknown Wi-Fi peripherals,thus above Smart Connectivity Setup Protocol settings are final.

Connectivity settings for the peripheral printer 100E are generated bythe Smart Connectivity Setup Protocol subroutine and returned. In thisexample, the network configuration program 144 keeps the connection tothe access point 100B.

The Wireless Docking Protocol 142 procedure buffers the connectivitysettings for the peripheral printer 100E in the connectivity settingstransmit buffer 148 in the Docking Station 100F. The connectivitysettings for connecting the peripheral printer 100E to the access point100B are then transmitted from the Docking Station 100F to the Dockeedevice 100A in step 408.

If the peripheral printer 100E is connected to Dockee 100A (Scenario 3of FIG. 2D) on path 510B, then the Wireless Docking Protocol 142procedure changes the connection to the Docking Station 100F and passesthe gathered information received from the Dockee device 100A to theSmart Connectivity Setup Protocol subroutine that is used as the networkconfiguration program 144 in this example.

For (Scenario 3 of FIG. 2D) on path 510B, Docking Station 100F definesmost optimal connectivity settings based on received information.

Important information is that Dockee 100A is single stack and Wi-FiDirect network link 120 is available (Dockee is able to use that) andone peripheral (Wi-Fi printer 100E) is accessible through that networklink 120.

However, in this scenario this original Wi-Fi Direct network 216 is notoptimal anymore, thus Docking Station 100F creates new Wi-Fi Directnetwork 218.

Docking Station 100F defines the following settings and rules fornetwork configuration program 144 for optimal connectivity in thewireless docking environment:

-   -   Dockee 100A may continue using new Wi-Fi Direct connection 120        (created in first phase).    -   Dockee 100A may access Internet by using new Wi-Fi Direct        connection 120 (if can be provided by the Docking Station 100F).    -   Peripheral Wi-Fi printer 100E connectivity settings 216 are not        valid anymore (new WPS procedure*) may be performed to        reconfigure Wi-Fi printer 100E if that printer is wanted to be a        peripheral within docking environment. Dockee gives necessary        guidance to user via UI to perform WPS procedure.

Connectivity settings for the peripheral printer 100E are generated bythe Smart Connectivity Setup Protocol subroutine and returned. TheWireless Docking Protocol 142 procedure buffers the connectivitysettings for the peripheral printer 100E in the connectivity settingstransmit buffer 148 in the Docking Station 100F. The connectivitysettings for connecting the peripheral printer 100E to the DockingStation 100F are then transmitted from the Docking Station 100F to theDockee device 100A in step 408.

If Step 508 determines that there is no existing internet connection onpath 508B, then it passes to step 512 that determines on path 512Awhether the peripheral printer 100E is not connected or on path 512Bwhether the peripheral printer 100E is connected to the Dockee 100A. Inboth paths, the Wireless Docking Protocol 142 procedure passes thegathered information received from the Dockee device 100A to the SmartConnectivity Setup Protocol subroutine that is used as the networkconfiguration program 144 in this example. Connectivity settings for theperipheral printer 100E are generated by the Smart Connectivity SetupProtocol subroutine and returned. The network configuration program 144in this example creates a connection to the Docking Station 100F. TheWireless Docking Protocol 142 procedure buffers the connectivitysettings for the peripheral printer 100E in the connectivity settingstransmit buffer 148 in the Docking Station 100F. The connectivitysettings for connecting the peripheral printer 100E to the DockingStation 100F are then transmitted from the Docking Station 100F to theDockee device 100A in step 408.

FIG. 5C continues the Wireless Docking Protocol 142 procedure of FIG.5A, where the Dockee 100A has a dual protocol stack and the plan is tocreate a new network with the Docking Station 100F. Step 514 determineswhether there is an existing internet access point 100B on path 514A orthere is no existing internet connection on path 514B (Scenario 5 ofFIG. 2F). In both paths, the Wireless Docking Protocol 142 procedurepasses the gathered information received from the Dockee device 100A tothe Smart Connectivity Setup Protocol subroutine that is used as thenetwork configuration program 144 in this example.

For path 514B (Scenario 5 of FIG. 2F), Docking Station 100F defines mostoptimal connectivity settings based on received information;

Important information is that Dockee 100A is single stack device. But inthis case Docking Station 100F does not have any information about otherWi-Fi networks, thus Docking Station 100F issues commands to use thenewly created Wi-Fi Direct network 120 for everything:

-   -   Dockee 100A may continue using the new Wi-Fi Direct connection        120 (created in first phase).    -   Dockee 100A may access Internet by using new Wi-Fi Direct        connection 120 (if it can be provided by the Docking Station        100F).    -   New peripherals may use new Wi-Fi Direct network 120.

The Docking Station 100F also commands the Dockee 100A to perform a newWPS in step 3 towards the peripherals (e.g., printer 100E), since theperipherals need the Credentials of the new Wi-Fi Direct network. Dockee100A then may perform WPS towards peripherals by using WPS (any methodavailable on the peripheral) in step 3, see details e.g. from scenario3. Dockee 100A may perform this WPS on behalf of Docking Station 100F*)to create Wi-Fi Direct link 230 in step 4. Dockee 100A gives necessaryguidance to user via user interface UI to perform these WPS procedures.

The Smart Connectivity Setup Protocol subroutine creates a connection tothe Docking Station 100F. Connectivity settings for the peripheralprinter 100E are generated by the Smart Connectivity Setup Protocolsubroutine and returned. The Wireless Docking Protocol 142 procedurebuffers the connectivity settings for the peripheral printer 100E in theconnectivity settings transmit buffer 148 in the Docking Station 100F.The connectivity settings for connecting the peripheral printer 100E tothe Docking Station 100F are then transmitted from the Docking Station100F to the Dockee device 100A in step 408.

FIG. 5D continues the Wireless Docking Protocol 142 procedure of FIG.5A, where the Dockee 100A has a dual protocol stack and a DockingStation 100F is to be added to an existing network.

Step 516 determines whether there is an existing internet access point100B on path 516A or there is no existing internet connection on path516B. Path 516A, there is an existing internet access point 100B, passesto step 518 that determines on path 518A whether the peripheral printer100E is connected to access point 100B (Scenario 2 of FIG. 2C) or onpath 518B whether the peripheral printer 100E is connected to Dockee100A (Scenario 4 of FIG. 2E).

If the peripheral printer 100E is connected to access point 100B(Scenario 2 of FIG. 2C) on path 518A, then the Wireless Docking Protocol142 procedure passes the gathered information received from the Dockeedevice 100A to the Smart Connectivity Setup Protocol subroutine that isused as the network configuration program 144 in this example.

For (Scenario 2 of FIG. 2C) on path 518A, Docking Station defines mostoptimal connectivity settings based on received information.

Important information is that Dockee 100A″ is dual stack andInfrastructure network is available and used by the Dockee andperipheral (Wi-Fi printer 100E). Also that Infrastructure network isused for Internet connectivity.

Docking Station 100F defines the following settings and rules fornetwork configuration program 144 for optimal connectivity in thewireless docking environment:

-   -   Dockee 100A″ may use new Wi-Fi Direct connection 120″ only for        accessing peripherals attached directly to Docking Station (e.g.        remote display, USB devices etc.)    -   Dockee 100A″ may continue accessing Internet by using existing        Infrastructure connection 210.    -   Peripheral Wi-Fi printer 100E may use current Infrastructure        connectivity settings over link 212 (no need to perform WPS for        reconfiguring Wi-Fi printer)    -   New peripherals may use new Wi-Fi Direct network (not any in        this scenario)

Note: Docking Station 100F joins to Wi-Fi AP (Infrastructure) usingCredentials received from the Dockee only when some another single stackDockee starts to use docking environment, or when Docking Station byitself needs Internet connectivity.

In this scenario user does not add any unknown Wi-Fi peripherals, thusabove network configuration program 144 settings are also final ones.

The Smart Connectivity Setup Protocol subroutine keeps the connection tothe access point 100B. Connectivity settings for the peripheral printer100E are generated by the Smart Connectivity Setup Protocol subroutineand returned. The Wireless Docking Protocol 142 procedure buffers theconnectivity settings for the peripheral printer 100E in theconnectivity settings transmit buffer 148 in the Docking Station 100F.The connectivity settings for connecting the peripheral printer 100E tothe access point 100B are then transmitted from the Docking Station 100Fto the Dockee device 100A in step 408.

If the peripheral printer 100E is connected to Dockee 100A (Scenario 4of FIG. 2E) on path 518B, then the Wireless Docking Protocol 142procedure passes the gathered information received from the Dockeedevice 100A to the Smart Connectivity Setup Protocol subroutine that isused as the network configuration program 144 in this example.

For (Scenario 4 of FIG. 2E) on path 518B, Docking Station 100F definesmost optimal connectivity settings based on received information.

Important information is that Dockee 100A″ is dual stack and twodifferent networks are used. Infrastructure network with access point100B is used for Internet connectivity.

Docking Station defines the following settings and rules for networkconfiguration program 144 for optimal connectivity in the wirelessdocking environment:

-   -   Dockee 100A″ may use new Wi-Fi Direct connection 120″ only for        accessing peripherals attached directly to Docking Station 100F        (e.g. remote display, USB devices etc.). Also Wi-Fi printer 100E        would be attached directly over link 224 to Docking Station 100F        in this case.    -   Dockee 100A″ may continue accessing Internet by using existing        Infrastructure connection over link 226 to the access point        100B.    -   Peripheral Wi-Fi printer 100E connectivity settings 220 are not        valid anymore (new WPS procedure) may be performed to        reconfigure Wi-Fi printer 100E if that printer is wanted to be a        peripheral within docking environment. Dockee 100A″ gives        necessary guidance to user via UI to perform WPS procedure.    -   New peripherals may use new Wi-Fi Direct network (not any in        this scenario)

Note: Docking Station 100F joins to Wi-Fi AP (Infrastructure) usingCredentials received from the Dockee 100A″ only when some another singlestack Dockee starts to use docking environment, or when Docking Stationby itself needs Internet connectivity.

In this scenario user does not add any unknown Wi-Fi peripherals, thusabove network configuration program 144 settings are also final ones.

The Smart Connectivity Setup Protocol subroutine changes the connectionto the Docking Station 100F. Connectivity settings for the peripheralprinter 100E are generated by the Smart Connectivity Setup Protocolsubroutine and returned. The Wireless Docking Protocol 142 procedurebuffers the connectivity settings for the peripheral printer 100E in theconnectivity settings transmit buffer 148 in the Docking Station 100F.The connectivity settings for connecting the peripheral printer 100E tothe Docking Station 100F are then transmitted from the Docking Station100F to the Dockee device 100A in step 408.

If Step 516 determines that there is no existing internet connection onpath 516B, then it passes to step 520 that determines on path 520Awhether the peripheral printer 100E is not connected or on path 520Bwhether the peripheral printer 100E is connected to the Dockee 100A. Inboth paths, the Wireless Docking Protocol 142 procedure passes thegathered information received from the Dockee device 100A to the SmartConnectivity Setup Protocol subroutine that is used as the networkconfiguration program 144 in this example.

The Smart Connectivity Setup Protocol subroutine creates a connection tothe Docking Station 100F. Connectivity settings for the peripheralprinter 100E are generated by the Smart Connectivity Setup Protocolsubroutine and returned. The Wireless Docking Protocol 142 procedurebuffers the connectivity settings for the peripheral printer 100E in theconnectivity settings transmit buffer 148 in the Docking Station 100F.The connectivity settings for connecting the peripheral printer 100E tothe Docking Station 100F are then transmitted from the Docking Station100F to the Dockee device 100A in step 408.

FIG. 5E continues the Wireless Docking Protocol 142 procedure of FIG.5A, where the Dockee 100A has a dual protocol stack and the plan is tocreate a new network with the Docking Station 100F. Step 522 determineswhether there is an existing internet access point 100B on path 522A(Scenario 6 of FIG. 2G) or there is no existing internet connection onpath 522B. In both paths, the Wireless Docking Protocol 142 procedurepasses the gathered information received from the Dockee device 100A tothe Smart Connectivity Setup Protocol subroutine that is used as thenetwork configuration program 144 in this example.

For path 522A (Scenario 6 of FIG. 2G), Docking Station 100F defines themost optimal connectivity settings based on the received information.Important information is that Dockee 100A″ is a dual stack device. Butin this case Docking Station 100F does not have any information aboutother Wi-Fi networks*), thus Docking Station 100F issues commands to usethe newly created Wi-Fi Direct network link 120″ for everything: *)Docking Station 100F is not aware of Infrastructure network access point100B or at least does not have credentials of the Infrastructurenetwork, thus it cannot use that network. However, if either Dockee100A″ or Docking Station 100F has detected this Infrastructure networkaccess point 100B by the scanning, then Docking Station 100F may givesome guidance to user, e.g. to perform WPS towards AP 100B withinWDP_SCS_Response.

-   -   Dockee 100A″ may continue using new Wi-Fi Direct connection 120″        (created in first phase).    -   Dockee 100A″ may access Internet by using new Wi-Fi Direct        connection 120″ and infrastructure link 236 (if it can be        provided by the Docking Station 100F).    -   New peripherals may use new Wi-Fi Direct network 120″.

If the user has performed WPS in step 3 between Dockee 100A and AP 100B,the Dockee should report this to the Docking Station 100F (e.g. withinWDP_Complete_Request).

Then Docking Station 100F checks whether initial configurations wereoptimal (=created Wi-Fi Direct network).

But, in this scenario, only Wi-Fi AP 100B provides InternetConnectivity, thus the Infrastructure network link 234 may be also beused for wireless docking environment. So Docking Station 100F may needto define new rules for network configuration program 144. New settingsmay be sent within WDP_Setup_Response to the Dockee:

-   -   Dockee may use new Wi-Fi Direct connection 120″ for accessing        peripherals, e.g. printer 100E, attached directly to Docking        Station 100F (e.g. remote display, USB devices etc.). Also Wi-Fi        printer 100E may be attached directly to Docking Station 100F in        this case.    -   Dockee 100A″ may access Internet by using new Infrastructure        connection 234.

The Smart Connectivity Setup Protocol subroutine creates a connection tothe Docking Station 100F. Connectivity settings for the peripheralprinter 100E are generated by the Smart Connectivity Setup Protocolsubroutine and returned. The Wireless Docking Protocol 142 procedurebuffers the connectivity settings for the peripheral printer 100E in theconnectivity settings transmit buffer 148 in the Docking Station 100F.The connectivity settings for connecting the peripheral printer 100E tothe Docking Station 100F are then transmitted from the Docking Station100F to the Dockee device 100A in step 408.

Wireless Docking Protocol in the Dockee Device

In example embodiments of the invention, the Docking Station 100F mayuse the Smart Connectivity Setup protocol to command the Dockee device100A to perform a Wi-Fi Protected Setup (WPS) procedure with certainperipheral devices. The Smart Connectivity Setup protocol within theDockee, for example in a mobile phone, may either provide instructionsto the user on a user interface, when human action is needed oralternately may automatically take needed actions without userinteraction, when possible.

The Dockee device 100A and the Docking Station 100F are Wi-FiDirect-devices that may create peer-to-peer connections betweenthemselves and other Wi-Fi Direct devices. Wi-Fi Direct Device Discoveryand Service Discovery features allow the Dockee device 100A to identifyavailable devices and services, such as the printer 100E, and reportthem to the Docking Station 100F before establishing a connection. TheDockee device 100A and the Docking Station 100F may use Wi-Fi ProtectedSetup to create connections between devices.

In the Wireless Docking Protocol 142, the Docking Station 100F will bethe Group Owner (GO) that manages the Group that includes the Dockee100A and peripherals, such as the printer 100E. Both the Dockee device100A and the Docking Station 100F include a Wi-Fi Protected SetupInternal Registrar functionality for communication between Clients inthe Group.

In the Wireless Docking Protocol 142, the Dockee device 100A and theDocking Station 100F support Discovery mechanisms. Device Discovery isused by the Dockee device 100A to identify other Wi-Fi Direct devices byusing a scan similar to that used to discover infrastructure accesspoints. Wi-Fi Protected Setup may be used to obtain credentials andauthenticate other Wi-Fi Direct devices. Service Discovery enables theDockee device 100A to receive advertisements of services supported byhigher layer applications of other Wi-Fi Direct devices, such as printer100E. Service Discovery may be performed at any time (e.g. even before aconnection is formed) with any other discovered Wi-Fi Direct device.

FIG. 6 is an example flow diagram 600 of operational steps of an exampleembodiment of the Wireless Docking Protocol 142 procedure in the Dockeedevice 100A, to transmit to the docking station, information it hasgathered about the dockee device's capabilities and characteristics ofone or more wireless devices within a wireless docking group; andreceive from the docking station, information to enable formation of theone or more optimal connections for the one or more devices in thewireless docking group, according to an embodiment of the presentinvention. The steps of the flow diagram 600 represent computer codeinstructions stored in the RAM and/or ROM memory of the Dockee device100A, which when executed by the central processing units (CPU), carryout the functions of the example embodiments of the invention. The stepsmay be carried out in another order than shown and individual steps maybe combined or separated into component steps. Additional steps may beinserted into this sequence. The steps of the example method are asfollows.

Step 602: forming a communication link between a wireless dockingstation and a dockee device;

Step 604: transmitting, by the dockee device to the docking station,information about the dockee device's capabilities and characteristicsof one or more wireless devices within a wireless docking group; and

Step 606: receiving, by the dockee device from the docking station,information to enable formation of the one or more optimal connectionsfor the one or more devices in the wireless docking group.

Using the description provided herein, the embodiments may beimplemented as a machine, process, or article of manufacture by usingstandard programming and/or engineering techniques to produceprogramming software, firmware, hardware or any combination thereof.

Any resulting program(s), having computer-readable program code, may beembodied on one or more computer-usable media such as resident memorydevices, smart cards or other removable memory devices, or transmittingdevices, thereby making a computer program product or article ofmanufacture according to the embodiments. As such, the terms “article ofmanufacture” and “computer program product” as used herein are intendedto encompass a computer program that exists permanently or temporarilyon any computer-usable medium or in any transmitting medium whichtransmits such a program.

As indicated above, memory/storage devices include, but are not limitedto, disks, optical disks, removable memory devices such as smart cards,SIMs, WIMs, semiconductor memories such as RAM, ROM, PROMS, etc.Transmitting mediums include, but are not limited to, transmissions viawireless communication networks, the Internet, intranets,telephone/modem-based network communication, hard-wired/cabledcommunication network, satellite communication, and other stationary ormobile network systems/communication links.

Although specific example embodiments have been disclosed, a personskilled in the art will understand that changes can be made to thespecific example embodiments without departing from the spirit and scopeof the invention.

What is claimed is:
 1. A method, comprising: forming a communicationlink between a wireless docking station and a dockee device; receiving,by the docking station, from the dockee device, information about thedockee device's capabilities and characteristics of one or more wirelessdevices within a wireless docking group; defining, by the dockingstation, one or more optimal connections for one or more of the wirelessdevices in the wireless docking group, based on the receivedinformation; and transmitting, by the docking station, to the dockeedevice, information to enable formation of the one or more optimalconnections for the one or more devices in the wireless docking group.2. The method of claim 1, wherein the information is communicated usinga docking protocol.
 3. The method of claim 1, which further comprises:joining, by the wireless docking station, an infrastructure networkhaving an access point, using a first protocol stack and forming apeer-to-peer connection with the dockee device, using a second protocolstack.
 4. The method of claim 1, which further comprises: forming, bythe wireless docking station, direct connections with at least one ofthe one or more devices, based on the defined optimal connections. 5.The method of claim 1, wherein the communication link with the dockeedevice is a Wi-Fi direct network.
 6. The method of claim 1, wherein thecommunication link with the dockee device is a Tunneled Direct LinkSetup connection.
 7. An apparatus, comprising: at least one processor;at least one memory including computer program code; the at least onememory and the computer program code configured to, with the at leastone processor, cause the apparatus at least to: form a communicationlink with a dockee device; receive from the dockee device, informationabout the dockee device's capabilities and characteristics of one ormore wireless devices within a wireless docking group; define one ormore optimal connections for one or more of the wireless devices in thewireless docking group, based on the received information; and transmitto the dockee device, information to enable formation of the one or moreoptimal connections for the one or more devices in the wireless dockinggroup.
 8. The apparatus of claim 7, wherein the information iscommunicated using a docking protocol.
 9. The apparatus of claim 7,which further comprises: the at least one memory and the computerprogram code configured to, with the at least one processor, cause theapparatus at least to: join an infrastructure network having an accesspoint, using a first protocol stack and form a peer-to-peer connectionwith the dockee device, using a second protocol stack.
 10. The apparatusof claim 7, which further comprises: the at least one memory and thecomputer program code configured to, with the at least one processor,cause the apparatus at least to: form direct connections with at leastone of the one or more devices, based on the defined optimalconnections.
 11. The apparatus of claim 7, wherein the communicationlink with the dockee device is a Wi-Fi direct network.
 12. The apparatusof claim 7, wherein the communication link with the dockee device is aTunneled Direct Link Setup connection.
 13. A computer program productcomprising computer executable program code recorded on a computerreadable, non-transitory storage medium, the computer executable programcode, when executed by a computer processor, comprising: code forforming a communication link between a wireless docking station and adockee device; code for receiving, by the docking station, from thedockee device, information about the dockee device's capabilities andcharacteristics of one or more wireless devices within a wirelessdocking group; code for defining, by the docking station, one or moreoptimal connections for one or more of the wireless devices in thewireless docking group, based on the received information; and code fortransmitting, by the docking station, to the dockee device, informationto enable formation of the one or more optimal connections for the oneor more devices in the wireless docking group.
 14. A method, comprising:forming a communication link between a wireless docking station and adockee device; transmitting, by the dockee device to the dockingstation, information about the dockee device's capabilities andcharacteristics of one or more wireless devices within a wirelessdocking group; and receiving, by the dockee device from the dockingstation, information to enable formation of the one or more optimalconnections for the one or more devices in the wireless docking group.15. The method of claim 14, wherein the information is communicatedusing a docking protocol.
 16. The method of claim 14, furthercomprising: forming, by the dockee device, one or more wirelessconnections with one or more other devices based on the receivedinformation.
 17. An apparatus, comprising: at least one processor; atleast one memory including computer program code; the at least onememory and the computer program code configured to, with the at leastone processor, cause the apparatus at least to: form a communicationlink between the apparatus and a wireless docking station; transmit tothe docking station, information about the apparatus' capabilities andcharacteristics of one or more wireless devices within a wirelessdocking group; and receive from the docking station, information toenable formation of the one or more optimal connections for the one ormore devices in the wireless docking group.
 18. The apparatus of claim17, wherein the information is communicated using a docking protocol.19. The apparatus of claim 17, further comprising: the at least onememory and the computer program code configured to, with the at leastone processor, cause the apparatus at least to: form one or morewireless connections with one or more other devices based on thereceived information.
 20. A computer program product comprising computerexecutable program code recorded on a computer readable, non-transitorystorage medium, the computer executable program code, when executed by acomputer processor, comprising: code for forming a communication linkbetween a wireless docking station and a dockee device; code fortransmitting, by the dockee device to the docking station, informationabout the dockee device's capabilities and characteristics of one ormore wireless devices within a wireless docking group; and code forreceiving, by the dockee device from the docking station, information toenable formation of the one or more optimal connections for the one ormore devices in the wireless docking group.